Open
Bug 940243
Opened 11 years ago
Updated 6 hours ago
XML View Source flags doctype after an XML declaration as an error
Categories
(Core :: DOM: HTML Parser, defect, P3)
Core
DOM: HTML Parser
Tracking
()
NEW
People
(Reporter: hsivonen, Unassigned)
References
()
Details
(Whiteboard: [domcore-bugbash-triaged])
From http://stackoverflow.com/questions/19849648/stray-doctype-error-in-firefox-source-code-viewer
View Source marks the doctype as an error. It shouldn't.
Hi,
The same issue occurs for an XML document using an XSL to produce HTML.
First the DOCTYPE is flagged as "stray doctype" in the source viewer.
I commented it out, and then I got a console error for the XSL line:
> InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable
A second problem (maybe a consequence) is that relative links don't work correctly for XML+XSL producing HTML output.
Example: http://www.growthcharts.info/support/helpfiles/growthcharts.xml#faq
When the page is loaded, the link doesn't work.
Then, if you click on the link address bar and hit Enter again, it goes straight to the right place.
Thanks,
Marius
Reporter | ||
Updated•6 years ago
|
Assignee: hsivonen → nobody
Priority: -- → P3
The same issue occurs if BOM (the byte order mark) of UTF-8 is set at the HTML start twice. Which can be produced by server scripts including (line include or require statements in PHP).
Reporter | ||
Comment 3•6 years ago
|
||
(In reply to arcadius from comment #2)
The same issue occurs if BOM (the byte order mark) of UTF-8 is set at the HTML start twice. Which can be produced by server scripts including (line include or require statements in PHP).
That's an actual error and should be flagged as such.
Updated•2 years ago
|
Severity: normal → S3
Comment 4•6 hours ago
|
||
Behavior is still the same, using the test case URL. You can't directly link to view source, so you have to open the page and right click then do view source.
Whiteboard: [domcore-bugbash-triaged]
You need to log in
before you can comment on or make changes to this bug.
Description
•