53401 - View Source broken on winNT

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect, P3)

Description

[sairuh (rarely reading bugmail)]

bill, do reassign if needed. for all i know, my winNT box might have its own
personal demon that's causing this *shrug* anyhow... found this using
2000.09.20.09 opt comm bits. not a problem on mac or linux.

1. go to any web page, eg, http://www.mozilla.org/
2. bring up the source window, either by Ctrl+U, View > Page Source main menu,
or by the context menu.

results: the source window only displays <html><body></body></html>

i've tried this with an existing profile, a new profile, after restarting the
app, in both modern and classic themes...

Comment 1

[sairuh (rarely reading bugmail)]

really should be fixed soon... i'll doublecheck this after doing a clean
install...

Comment 2

[sairuh (rarely reading bugmail)]

i am baffled. after a clean install, this still happens to me. i've even checked
in both themes. for some reason, this works for shrir --although for him, the
source page is initially blank. after clicking in the window, the source does
appear.

this blocks my source window testing on winNT --at least on my machine. arrgh.

Comment 3

[rubydoo123]

view source looks fine on win98

Comment 4

[Phil Peterson]

need info. is this broken for everyone, or just sairuh?

Comment 5

[John Morrison]

This is broken for me on win2k 2000092005 (this morning's opt. verif build). 

I get this exception:
JavaScript error:
 line 0: uncaught exception: [Exception... "Not enough arguments 
[nsIWebNavigation.loadURI]"  nsresult: "0x80570001 
(NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "
JS frame :: chrome://navigator/content/viewsource.js :: onLoadViewSource :: 
line 51"  data: no]
Document about:blank loaded successfully

That interface, and the corresponding call in viewsource.js, were changed by 
Adam Lock before the build this morning, and it looks right, but something
is not working right. Perhaps this is just an error with this build?

At any rate, I think Adam knows where to look.

Comment 6

[Adam Lock]

It works for me.

Did you clobber or build from fresh? Perhaps the XPT files do not get 
overwritten correctly or there are no proper dependency checks when you build 
over an older release.

Comment 7

[Adam Lock]

To clarify my last comment Did you build from a fresh pristine tarball or one 
that had been clobbered, possibly leaving something behind that shouldn't have 
been such as a JAR file?

If the latter, can you clean out all the JAR files from mozilla/xpfe and try 
building that directory again?

Comment 8

[sairuh (rarely reading bugmail)]

fwiw, i don't see this on win98 using the mozilla optimized 2000.09.21.08 bits. 
adam, on winNT i'm grabbing the optimized (verification) bits from sweetlou (i'm 
not building 'em).

jrgm, d'you see this with today's bits on win2k or winNT? (i'm telecommuting 
today so only have access to win98 mozilla opt bits.)

Comment 9

[John Morrison]

This works on NT for today's opt. builds. I assume it was just a hiccup in 
the build machines, possibly since the first win32 build kicked off 20 
minutes prior to Adam's checkin. (This should have been cool, but something
was not right). Anyways, WORKSFORME.

Comment 10

[sairuh (rarely reading bugmail)]

vrfy wfm using 2000.09.22.08 comm bits on winnt. whew.