348552 - Malformed XHTML View Source Shows Source of Error Page

Status: VERIFIED INVALID

(Toolkit :: View Source, defect)

Description

[Jamie Thompson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5

When you attempt to load a xhtml page that is malformed, firefox quite correctly displays an error page with the (rather unhelpful) line the error occurred on.

If you then attempt to view said source, you instead get the source of the error page, rather than the malformed source Firefox actually received. this make tracking down what exactly has gone wrong much harder than it needs to be, so much so infact that I've had to resort to sending pages as text/html and using a HTML Validator plugin so I have a chance to actually view the malformed content.

As a side note, it'd be nice if the error page displayed a few lines before and after the error line, so as to provide some context.

Reproducible: Always

Steps to Reproduce:
1. Open a malformed xhtml page sent with the correct mime-type so Firefox treats it as xhtml
2. Click view source
3. Observe source of error page

Actual Results:  
Source of Firefox's xml error page is displayed.

Expected Results:  
Displayed the malformed source page as it recieved it. Potentially highlighting the point where the page is malformed.

Comment 1

[crf]

Attachment: test case.

using Mozilla/5.0 (Windows; U; Win98; en-GB; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6

I didn't see this happen in a test case I made (I hope it works here). Right-click-->View page source showed the text of the web page it was trying to understand. As did View menu--> Page source.

Could the reporter show a url or test case where it occurs?

===

Comment 2

[Jamie Thompson]

My apoligies...it doesn't seem to be doing this anymore, even on my work machine where I was experiencing it. How strange. My guess is that it must've been one of my web dev extensions being naughty and perhaps somehow pushing the error page into the cache.

My apoligies for seemingly wasting your time.