121006 - XUL files can't be displayed

Status: RESOLVED INCOMPLETE

(Other Applications Graveyard :: Venkman JS Debugger, defect)

Description

[Christian :Biesinger (don't email me, ping me on IRC)]

When starting venkman with "Initialize at startup" enabled, the filelist
contains many XUL files.
However, when clicking on them, their contents are not displayed.

(self-compiled build 2002011913)

Comment 1

[André Dahlqvist]

Since you mention "Initialize at startup" being enabled, do you mean that this
works with that option disabled?

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

Just checked; and no, it doesn't work either with "Init at startup" disabled.

Comment 3

[Robert Ginda]

This looks to be a problem when the xul is jar'd.  It seems to work for me with
unjar'd chrome, but I get a one line file, with no text, when the chrome is in a
jar file.

Comment 4

[Robert Ginda]

I think this got fixed with brendan's massive bug 68045 patch.

Comment 5

[Robert Ginda]

The bug mentioned in my last comment wasn't responsible for fixing this problem,
but it appears to be fixed just the same.  Please reopen if you can reproduce.

Comment 6

[Christian :Biesinger (don't email me, ping me on IRC)]

as a matter of fact, I can reproduce, at least with some files - neither
calendar.xul nor navigator.xul are displayed, but messengercompose.xul works
(seems to be the recycled, hidden window).
(this is when double-clicking on the file in the Windows-list)

Comment 7

[Ian Neal]

I also see this on BuildID 2003072904 on WinXP -> OS to All

Comment 8

[Rob North]

See this on Firefox 1.0
Could the underlying cause be Bug 206691?
Which implies only cached XUL will be affected.

Comment 9

[James Ross]

Current Venkman still has this problem, but it does seem likely that bug 206691 is the cause. Marking dependancy until better investigation can be done.

Comment 10

[BMO Automation]

Component is obsolete so resolving bugs as INCOMPLETE