641898 - View source returns one line, other browsers return correctly

Status: REOPENED

(Toolkit :: View Source, defect)

Description

[Nick]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0

Clicking view source for the page returns: {"mode":"build"}. All others return correctly.

Reproducible: Always

Steps to Reproduce:
1. Goto the page
2. Click view source
Actual Results:  
Returned: {"mode":"build"}

Expected Results:  
Returned the correct HTML. Do this in chrome (10.0.648.133 beta is what I'm using) and it return correctly.

Comment 1

[David Dahl :ddahl]

Not sure why this is happening on this page

Comment 2

[juan becerra [:juanb]]

If you view source as it is loading, you can see a different source than what you see when it is fully loaded.

Comment 3

[David Dahl :ddahl]

In the Web Console, document.body.innerHTML gives you the source. The entire doc must be built by script.

Comment 4

[Nick]

(In reply to comment #2)
> If you view source as it is loading, you can see a different source than what
> you see when it is fully loaded.

no its fully loaded

Comment 5

[Nick]

(In reply to comment #3)
> In the Web Console, document.body.innerHTML gives you the source. The entire
> doc must be built by script.

But still, why cant Firefox do this when EVERYOTHER browser can. Tested on IE 8, Chrome, and Safari.

Comment 6

[David Dahl :ddahl]

(In reply to comment #5)
> (In reply to comment #3)
> > In the Web Console, document.body.innerHTML gives you the source. The entire
> > doc must be built by script.
> 
> But still, why cant Firefox do this when EVERYOTHER browser can. Tested on IE
> 8, Chrome, and Safari.

That will depend on what the view-source code is doing[1] and - perhaps in what the content scripts are doing on this page

[1] http://mxr.mozilla.org/mozilla-central/source/toolkit/components/viewsource/content/viewSource.js#120

Comment 7

[Philip Chee]

Works for me:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b13pre) Gecko/20110310 Firefox/4.0b13pre SeaMonkey/2.1b3pre

Using View->Page Source.

Comment 8

[Philip Chee]

> The entire doc must be built by script.
I turned javascript off. View source still works fine.

Comment 9

[Nick]

Yes. Is there any other debug information I can send you?

(In reply to comment #7)
> Works for me:
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b13pre) Gecko/20110310
> Firefox/4.0b13pre SeaMonkey/2.1b3pre
> 
> Using View->Page Source.

Comment 10

[Nick]

Also, your not using RC1.

(In reply to comment #7)
> Works for me:
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b13pre) Gecko/20110310
> Firefox/4.0b13pre SeaMonkey/2.1b3pre
> 
> Using View->Page Source.

Comment 11

[Nick]

Same here using safari.

Comment 12

[Philip Chee]

> Also, your not using RC1.
There are no changes between trunk and Firefox RC1 except for Android specific changes. Are you testing on Firefox Mobile 4.0?

Also Nick, are you testing with Firefox in safe mode?
<http://support.mozilla.com/en-US/kb/Safe%20Mode>

Comment 13

[Nick]

Hmm, I would have thought more would have changed in the trunk since rc1. Oh well. Also, no I am not running mobile firefox, and am not using safe mode on either windows or firefox.

(In reply to comment #12)
> > Also, your not using RC1.
> There are no changes between trunk and Firefox RC1 except for Android specific
> changes. Are you testing on Firefox Mobile 4.0?
> 
> Also Nick, are you testing with Firefox in safe mode?
> <http://support.mozilla.com/en-US/kb/Safe%20Mode>

Comment 14

[Philip Chee]

Nick, this is a hint for you to run your test case while Firefox is in safe mode!

Comment 15

[Nick]

I would have but can't at the moment. It might actually be a while, possibly 2 days before I can.

(In reply to comment #14)
> Nick, this is a hint for you to run your test case while Firefox is in safe
> mode!

Comment 16

[Nick]

Disreguard the last post, appearently it's also an issue on the max rc. Running in safe
mode doesn't help. 

Also, nice job Mozilla with the UI on the mac, I like it a lot more.

(In reply to comment #14)
> Nick, this is a hint for you to run your test case while Firefox is in safe
> mode!

Comment 17

[Rob Campbell [:rc] (:robcee)]

select-all, right click and select View Selection Source from the context menu.

Comment 18

[Philip Chee]

w00t I see it now on trunk (I pull and do a new build almost every day). View Selection Source works but this is a workaround really. Rob I suggest reopening.

Also in Console2:

Error: attempt to run compile-and-go script on a cleared scope
Source file: http://marblerun.at/javascripts/marblerun-compiled.js?1299680283
Line: 677

Warning: Empty string passed to getElementById().
Source file: http://marblerun.at/tracks/new

Error: event.findElement is not a function
Source file: http://marblerun.at/javascripts/prototype.js?1299680283
Line: 5680

Error: Illegal operation on WrappedNative prototype object = NS_ERROR_XPC_BAD_OP_ON_WN_PROTO
Source file: http://marblerun.at/javascripts/marblerun-compiled.js?1299680283
Line: 677

Comment 19

[David Dahl :ddahl]

(In reply to comment #17)
> select-all, right click and select View Selection Source from the context menu.

I'm not sure this should be closed until we figure out what is actually happening. I assume it is some kind of hack in the content script - perhaps we ask the author of the page what kind of unconventional scripting is happening here?

Comment 20

[Rob Campbell [:rc] (:robcee)]

ok, reopened.

Philip, I think you were probably seeing the first-run content on previous loads. They popup a div on screen before doing whatever they're doing to initializing the page on subsequent loads. They're probably storing a cookie.

Further investigation required, I guess.

Comment 21

[Nick]

Sorry I haven't been here, just got back from camping. Have you found anything new?