This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html Multipage: http://www.whatwg.org/C#parsing-main-inframeset Complete: http://www.whatwg.org/c#parsing-main-inframeset Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html Comment: html tag in frameset shouldn't be ignored? Posted from: 67.188.68.182 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36
Can you elaborate?
Oh, bugzilla seems not able to capture the exact section I was referring. 12.2.5.4.20 The "in frameset" insertion mode, -> A start tag whose tag name is "html" Process the token using the rules for the "in body" insertion mode. Does that mean <frameset> <html> ... </html> </frameset> is actually allowed, and content inside the html tag would be considered as valid? Personally I think this is not required.
You can't conclude whether anything is allowed by reading the parser. The <frameset> element itself is not allowed, to begin with. But in general, the parser does things in a particular way in order to be compatible with what Web content expects (and what browsers have traditionally done). In this particular case, it is required to propagate the attributes on the <html> token to the root element. <frameset><html foo>
Ah, yeah, ignore the parser if you're trying to work out what's allowed or not. The section to read for that is the Syntax "Writing HTML" section, and the content model descriptions in the sections that describe the elements themselves. Does that resolve this bug?
Please reopen this bug if comment 4 doesn't resolve this issue to your satisfaction. Thanks.