Open Bug 373171 Opened 18 years ago Updated 2 years ago

Load images automatically should do what it says

Categories

(Core :: Graphics: Image Blocking, defect)

defect

Tracking

()

People

(Reporter: timeless, Unassigned)

References

()

Details

It's a bit hard to explain this bug. This is based on an expectation that it's impossible to explain to users the difference between images that are free and images which the user expects not to load automatically. It's unclear exactly how many users will ever use the feature to never show images, however some browsers make this option fairly prominent, and they also use e.g. a local (file:) start page, which means that the first page at the first opportunity will behave in a way that seems "wrong". This is inconsistent with the other browser I tested. Mossop and I understand that the idea was to save bandwidth, but I'm more concerned with saving bug-width and parity with other browsers. Tested on Windows XP, Solaris Intel and Linux ARM :). The code for this bug is: http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/extensions/permissions/nsContentBlocker.cpp&rev=1.8&mark=157,166-173#140 well, "Ony" is just annoying according to Firefox 2.0.
mook contributes this which is probably a better url: data:text/html,<img%20src="jar:http://www.oxymoronical.com/site/files/844/default/1/cookieui-0.2.3.xpi!/chrome/skin/icon.png"> since it shows that in fact we will hit the network :)
So what is this bug about? Just removing support for this preference? Or something else?
no, we kinda need it to work. it just needs to mean that images in content shouldn't be loaded no matter where their source is (about:, data:, jar:, file:, gopher:, ....)
Oh, that. Fine, as long as you don't hurt perf and all. For a start, moving from a protocol list to protocol bits is a good idea, probably.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.