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/rendering.html Multipage: http://www.whatwg.org/C#frames-and-framesets Complete: http://www.whatwg.org/c#frames-and-framesets Comment: Define rendering for the <frameset> element as a normal element. Posted from: 82.161.179.17 by annevk@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.3; U; en) Presto/2.10.229 Version/11.62
In particular, just like you can have multiple <body> element children of the root element, or <p> children, or anything really, you can have multiple <frameset> element children, mix them with <body>, etc. and it should all work fine (and does in Gecko/WebKit/Trident). The only special thing is the rendering of <frameset>, which is the height of the viewport, etc.
See http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=1468 and http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=1469 for example
This bug was cloned to create bug 17928 as part of operation convergence.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/59df7cf6a5c71e305c770d66811b21e0bcb1c91c Rationale: accepted WHATWG change