Closed
Bug 745221
Opened 13 years ago
Closed 13 years ago
HTML stops rendering in frameset after so much text (and unclosed <font> tags) are added
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Terry.F1Com, Unassigned)
References
()
Details
(Other than missing character encoding labeling, the page validates. Adding character encoding does not change the bug.)
In Firefox 11, from this URL:
http://www.westchestercoinclub.org/
in the left frame click "In The News". Scroll down to:
April 25, 2011: ANA Rarities on Exhibit at PAN Show, May 6-8.
From there down, the HTML no longer renders correctly. Page breaks, horizontal lines, bolding, etc.
If the page creator adds info at the top of the page, then the next date up (May 24, 2011) becomes the starting point for non-rendered HTML.
This does not occur in Chrome, IE8, Opera, or FF3.
Problem can be observed directly on
http://www.westchestercoinclub.org/news.htm
Guessing Parser.
Component: Layout: HTML Frames → HTML: Parser
QA Contact: layout.html-frames → parser
Actually, this is probably just all the unclosed <font> tags making us hit the max nesting level.
(In reply to Terry R. from comment #0)
> (Other than missing character encoding labeling, the page validates.
Not really:
http://validator.w3.org/check?uri=http%3A//www.westchestercoinclub.org/news.htm
Summary: HTML stops rendering in frameset after so much text is added (validated code) → HTML stops rendering in frameset after so much text (and unclosed <font> tags) are added
(In reply to David Baron [:dbaron] from comment #5)
> (In reply to Terry R. from comment #0)
> > (Other than missing character encoding labeling, the page validates.
>
> Not really:
> http://validator.w3.org/check?uri=http%3A//www.westchestercoinclub.org/news.
> htm
Ah, I forgot the site was using frames when I copied the URL, which doesn't change the URL address.
I removed all the unclosed font tags and FF11 displays it correctly. Not counting the other browsers, I wonder why FF3 was so tolerant?
|
||
Comment 7•13 years ago
|
||
I believe with the HTML5 parser (in Firefox 4) we changed the way we handle overly-deep content nesting...
If the nesting level issue isn't considered a bug (as all other browsers display it fine), I will close the bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•