Closed
Bug 385589
Opened 18 years ago
Closed 16 years ago
can't view source of XUL loaded via URI bar
Categories
(Core Graveyard :: View Source, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 206691
People
(Reporter: eyalroz1, Assigned: mrbkap)
Details
- Enter some XUL chrome URI in the URI bar (e.g. chrome://messenger/content/ABSearchDialog.xul).
- View|Source .
- Window is empty; no errors in the console.
This may relate to bug 206691.
Comment 1•18 years ago
|
||
(In reply to comment #0)
> This may relate to bug 206691.
Sounds like a duplicate of bug 206691, to me.
Reporter | ||
Comment 2•18 years ago
|
||
Bug 206691 says "Need a _DEBUG_ build to reproduce." , and mine is not a debug build. Plus I don't get an error on the console like 206691 suggests I should be saying. As for whether that part of the chrome is 'cached xul' - I wouldn't know.
Comment 3•18 years ago
|
||
If (in about:config) you set nglayout.debug.disable_xul_cache to true (and you may have to restart and maybe also delete your XUL.mfl (or mfasl or whatever)) you should find that you can start viewing the source of chrome: XUL.
I don't think a debug build makes any difference, but excepting about:config the above preference is only exposed in SeaMonkey trunk nightly preference panels.
Comment 4•16 years ago
|
||
bug 206691 is now fixed -- is this one, or did it turn out not to be a dupe?
Reporter | ||
Comment 5•16 years ago
|
||
I guess it probably was a dupe after all.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•