FS#3747 - Firefox(1.5-3) - images still load when "Load Images" is unchecked

Attached to Project: Arch Linux
Opened by Daniel Hansen (rokaholic) - Wednesday, 11 January 2006, 21:29 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This problem seems very strange to me. In the official mozilla.org firefox 1.5 build for linux, this works fine. However, no matter what I do, in the arch build, it will always display images.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 13 January 2006, 14:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  firefox 1.5-3 comes with the default set of extensions now
Comment by Daniel Hansen (rokaholic) - Wednesday, 11 January 2006, 21:46 GMT
Here's a pastebin comparing the buildconfigs of the arch and mozilla builds -> http://pastebin.com/501521
Comment by Daniel Hansen (rokaholic) - Wednesday, 11 January 2006, 22:11 GMT
I have talked with someone on irc.mozilla.org and he mentioned it might have something to do with this -> http://lxr.mozilla.org/mozilla/source/extensions/permissions/nsContentBlocker.cpp#86
He also recommended i try this:

strings firefox-bin | grep permissions

Here's what I get for the official mozilla.org build:

@mozilla.org/permissions/contentblocker;1
permissions.default.

and what I get for arch's build:

(nothing)

So obviously somehow contentblocker is not getting built properly or something
Comment by Daniel Hansen (rokaholic) - Wednesday, 11 January 2006, 22:41 GMT
Someone on irc.mozilla.org mentioned that because the archbuild was configured with "--enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,typeaheadfind"(refer to link in first comment), it is possible that other extensions are not being built, since the ones that do get built are being explicity defined. The official build does not even use this, maybe a good idea would be to configure the build without this option altogether?
Comment by Jan de Groot (JGC) - Wednesday, 11 January 2006, 22:46 GMT
We need to specify this line in mozconfig to get typeaheadfind working in other browsers like epiphany and galeon. I hope XULRunner 1.8 final will be released soon, so we can build against that instead.
Comment by Jan de Groot (JGC) - Wednesday, 11 January 2006, 23:01 GMT
A new mozconfig file has been committed in CVS. When I get to a rebuild, the correct default extensions, with typeaheadfind, but without gnomevfs and reporter will get build.

Loading...