Closed
Bug 195625
Opened 23 years ago
Closed 9 years ago
browser.docShell.allowImages = false; also hides scrollbar images!
Categories
(Core Graveyard :: Embedding: APIs, defect)
Core Graveyard
Embedding: APIs
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bugs4hj, Assigned: adamlock)
Details
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3b; MultiZilla v1.3.1 (e))
Gecko/20030302
Steps to reproduce:
- set browser.docShell.allowImages = false;
- take a look at your scrollbar images
Current result : all chrome://global/skin//scrollbar/*.gif are gone
Expected Result: display all chrome: related images
Now, take a look at this:
http://lxr.mozilla.org/seamonkey/source/embedding/browser/webBrowser/nsWebBrowserContentPolicy.cpp#68
I think that nsIURI *contentLocation should be used to check for a chrome:
protocal first, and not simply return shell->GetAllowImages(shouldLoad);
Oh, just for the record:
prefs.setIntPref("network.image.imageBehavior", [1/2]); does not expose this bug!
Comment 2•23 years ago
|
||
I'm being blind... is Moz 1.3b supposed to have a
"browser.docShell.allowImages" pref? I did an lxr search and came up empty.
Josh, it's not a pref, just look at this:
http://lxr.mozilla.org/seamonkey/source/docshell/base/nsIDocShell.idl#216
Comment 4•23 years ago
|
||
Embedding apis.
Assignee: shliang → adamlock
Component: Browser-General → Embedding: APIs
QA Contact: pmac → carosendahl
I am nominating this bug for mozilla 1.6b because this bug still assists and
kills theme support. It should be easy to fix, because all it needs is a check
for chrome:
Flags: blocking1.6b+
Comment 7•22 years ago
|
||
HJ: only drivers can set (+) blocking flags. you can request (?) them.
Flags: blocking1.6b+
Hm, well I *can* set these flags, as you've noticed, but I guess I should not be
allowed to do so by bugzilla rights, however, thanks for the tip.
Updated•16 years ago
|
QA Contact: carosendahl → apis
Comment 9•9 years ago
|
||
Marking a bunch of bugs in the "Embedding: APIs" component INCOMPLETE in preparation to archive that component. If I have done this incorrectly, please reopen the bugs and move them to a more correct component as we don't have "embedding" APIs any more.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•