87918 - Cannot view xul source

Status: RESOLVED DUPLICATE of bug 206691

(SeaMonkey :: UI Design, defect)

Description

[joki (gone)]

Running Win2K we seem to just get a blank window these days when attempting a 
view-source on a xul doc.  I don't know if harishd is the right owner for this 
or not but he seems to own more view-source bugs than anybody else so I'll start 
with him.

Comment 1

[Boris Zbarsky [:bzbarsky]]

When doing this, I get the following error:

Error: redeclaration of const kIOServiceProgID
Source File: chrome://communicator/content/utilityOverlay.js
Line: 1

Also, I can load
view-source:chrome://communicator/content/pref/pref-appearance.xul just fine up
_until_ I have loaded chrome://communicator/content/pref/pref-appearance.xul

Over to XP apps, ccing doron and myself.  I think this is a dup....

Comment 2

[Boris Zbarsky [:bzbarsky]]

In fact it's a dup of bug 86238.

*** This bug has been marked as a duplicate of 86238 ***

Comment 3

[sairuh (rarely reading bugmail)]

v

Comment 4

[Boris Zbarsky [:bzbarsky]]

Hrm.  I suck.  Looks like that error appears even when we load the source correctly.

Nevertheless, it looks like we don't make it down to the parser when we try to
view source in this case.  So this should stay in XP app land for now.

Comment 5

[Boris Zbarsky [:bzbarsky]]

OK.  A bit of research shows the following:

1)  Once we've loaded the XUL doc in the browser window, further loads use the
    content type mozilla.application/cached-xul instead of
    application/vnd.mozilla.xul+xml

2)  The parser does not handle that mimetype in viewsource (so there _is_ some
    parser component to this bug).  But if I add this mimetype to the list of
    handled types I get the source of about:blank instead of the actual source I
    need to handle.

Still investigating this.

Comment 6

[Doron Rosenberg (IBM)]

seeing this on win98 too

Comment 7

[harishd]

Looks like an OnDataAvailable is not getting fired!

I see an OnStartRequest followed by an OnStopRequest and that's it. Data did not
flow into the parser.

Comment 8

[harishd]

CCing dougt.

Comment 9

[Doug Turner (:dougt)]

How do I reproduce this?

Comment 10

[Boris Zbarsky [:bzbarsky]]

Hmm.. Could the problem be caused by the code at
http://lxr.mozilla.org/seamonkey/source/content/xul/document/src/nsXULDocument.cpp#702
?

Though when we're viewing source the document is treated as an HTML document, so
this code may never even be called...

Comment 11

[Boris Zbarsky [:bzbarsky]]

To reproduce:

1)  Load chrome://communicator/content/pref/pref-appearance.xul in the browser
    window
2)  Select View > Page Source

To reproduce the desired behavior:

1)  Start a fresh mozillla
2)  Type view-source:chrome://communicator/content/pref/pref-appearance.xul in
    the URL bar

Comment 12

[Blake Ross]

Umm...since Harish accepted this, I take it this is supposed to be assigned to 
him...

Comment 13

[harishd]

Nope...this should probably go to dougt or darin.

Comment 14

[Doug Turner (:dougt)]

This is some xul cache problem as Boris suggested.  

If the XUL file is in the *xul* cache, there will not be any oda's.  Do we want 
endusers to be able to viewsource of XUL?  Reassigning to default owner.

Comment 15

[Blake Ross]

->doron

Comment 16

[Boris Zbarsky [:bzbarsky]]

Dupping forward to a bug with a clearer description of the problem.

*** This bug has been marked as a duplicate of 206691 ***