Closed
Bug 572208
Opened 15 years ago
Closed 15 years ago
[HTML5] Frameset page containing unprintable/unknown character anywhere before the <frameset> tag not rendered
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 563526
People
(Reporter: netrolller.3d, Unassigned)
References
Details
(Keywords: regression, testcase)
Attachments
(1 file)
|
127 bytes,
text/html
|
Details |
With the old HTML parser (html5.enable == false), the following testcase:
data:text/html,�<frameset><frame src="data:text/html,PASS">
renders PASS. However, with the HTML5 parser, the result is a missing-glyph symbol (rendered as questionmark-in-diamond rather than as hexbox, but this is a different bug). In fact, if any unprintable or unknown character comes before <frameset> in a framed document, the frames are not rendered.
This makes the configuration page of Dlink DSL-xxxT ADSL modems (and probably any other TI AR7 modem that uses frames for its configuration page) inaccessible in trunk builds (where HTML5 is on by default), as the source of the config page on these platforms begins with a null (\0, �, U+0000) character before <html>, resulting in a blank (sans the missing-glyph sign) page. Other AR7-based modems (ones that do not use frames) are also affected to a lesser extent: a missing-glyph is shown in the upper left corner, but other than that, the page is rendered correctly. The missing glyph character doesn't show up either with the old HTML parser.
|
Reporter | |
Updated•15 years ago
|
Blocks: html5-parsing
|
||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
|
||
Updated•14 years ago
|
blocking2.0: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•