32437 - View Source is broken. All you get is an empty window.

Status: VERIFIED FIXED

(SeaMonkey :: Installer, defect, P3)

Description

[Henrik Lynggaard Hansen]

to reproduce:
start mozilla
select help->about mozilla
when it has loaded select view->page source

what should happen:
I should get a window with the page source.

what does happen:
a empty window appear and the console window reads:
"
JavaScript Error: TypeError: Components.interfaces.nsIDocShell has no properties
URL: chrome://navigator/content/viewsource.js
Line number: 6
"

Comment 1

[Gervase Markham [:gerv]]

Upping severity. I also see this on W95 builds up to 20000318. 

As I have reports it works under Linux, and reporter does not give an OS, 
changing OS to W95.

Leaving as Browser-General. cbegle - any thoughts?

Gerv

Comment 2

[Adam]

Works for Mac OS build 2000031908.

Comment 3

[Asa Dotzler [:asa]]

WORKSFORME with 031908 win32 build under NT.  Is this a win95 specific problem?

Comment 4

[Henrik Lynggaard Hansen]

I saw it under win98

Comment 5

[Sean Richardson]

From comments in bug 32142, "view source displays a blank page", WORKSFORME,
this looks like a transitory packaging problem, and probably a DUP. 
The reported js error looks the same.

View>Page Source works for me with 2000-03-20-11-M15 and 2000-03-18-15-M15 on 
WinNT.

Comment 6

[Brian Krabbe]

this is broken for me on 2000032011 on Windows 2000.  Ive confirmed this on two
different machines.
not my bug so im not changing OS.

Comment 7

[Asa Dotzler [:asa]]

still unable to reproduce on winNT with 032011 build.  It does take a little
while to display the source but it displayed jsut fine.

Comment 8

[Gervase Markham [:gerv]]

Still seeing this under 95 2000032109. Must be 95/98 only. Every new build I 
have, I install into a clean directory, as [e-mail] recommends in Bug 
32142 (although I do have 10 different builds installed at the moment). How 
would I tell if it's not picking up the right components directory?

Gerv

Comment 9

[Christine Begle]

here's how to telll
- go to your bin directory
- type xpchell
- at the js prompt, type
  Components.interfaces.nsIDocShell.viewSource

  that should return 1

then, start Mozilla from the bin directory, and see if that works.  it should.
then start it from however you usually start it and see if it works.  

Comment 10

[Gervase Markham [:gerv]]

Under Windows, I don't have a bin directory, or any file called xpchell.* (or 
xpshell.*, for that matter anywhere on my drive. :-(

Gerv

Comment 11

[Asa Dotzler [:asa]]

[e-mail] what does your mozilla directory structure look like?

Comment 12

[Jeremy M. Dolan]

I think I can answer on gervase.markham's behalf. I have the latest nightly 
running on Win98 and my view source is also broken. He is correct, we have no 
bin/ or and files matching xpch*.*. Our directory structure is:

/ : contains a bunch of dll's, mozilla.exe, and component.reg
/chrome/ 
/components/
/defaults/
/Plugins/
/res/

all recent builds have had this structure. M14 had no /Plugins/ but had 
an /OutTestData/.

Comment 13

[Brian Krabbe]

i see the problem.  I think these guys are running the installer.  If you do 
that you dont get all the test executables in the bin directory.

Comment 14

[Jeremy M. Dolan]

Yes, I am running the installer. I assumed the smaller file size of the exe 
over the zip was due to the fact that ZIP type compression generally sucks, and 
the exe installer had a better built in compression. Does it explain anywhere 
that possibly useful testing tools aren't included with the EXE distribution? 
If it does, <b> it or something, cause I missed it =). I'll be getting the ZIP 
from now on.

Comment 15

[Jeremy M. Dolan]

With the latest build in the ZIP distribution, view source now works. Mac 
installer may break this too?

Comment 16

[Gervase Markham [:gerv]]

I tried a ZIP distribution and it worked. So this is a packaging problem. Moving 
to Installer: XPI Packages.

Summary: View Page Source not working on Installer versions of W95, W98 and 
Win2k only (not NT). The console error is given in the first comment.

Gerv

Comment 17

[Sean Su]

Found the problem.  It's a packaging problem.  The .zip file that contains the 
Seamonkey build has the two files required for view a page source:

  docshell.dll
  docshell_base.xpt

The Seamonkey windows installer does not have those files in its package.  I'll 
update the packages-win file appropriately and notify Travis (module owner) of 
my change.  This will fix the problem on all windows platforms.

Comment 18

[travis]

Looks good r=travis

Comment 19

[Sean Su]

fixed.

Comment 20

[sairuh (rarely reading bugmail)]

*** Bug 33248 has been marked as a duplicate of this bug. ***

Comment 21

[Grace Bush]

verified on ftp://ftp.mozilla.org/pub/mozilla/nightly/latest/2000-03-30-09M15 
build

Comment 22

[Matthias Versen [:Matti]]

mid-air collision ? / bugzilla cleanup
Reopening (current State: verfied and no resolution)

Comment 23

[Matthias Versen [:Matti]]

fixed

Comment 24

[Matthias Versen [:Matti]]

verfied