Closed Bug 385589 Opened 17 years ago Closed 15 years ago

can't view source of XUL loaded via URI bar

Categories

(Core Graveyard :: View Source, defect)

x86
Windows XP
defect
Not set
normal

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.
(In reply to comment #0)
> This may relate to bug 206691.

Sounds like a duplicate of bug 206691, to me.
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.
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.
bug 206691 is now fixed -- is this one, or did it turn out not to be a dupe?
I guess it probably was a dupe after all.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Product: SeaMonkey → Core Graveyard
You need to log in before you can comment on or make changes to this bug.