This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9055 - There is no direct replacement for a frameset. This supports some functionality and features that can't be emulated 100% by other methods. Server side includes cannot dynamically udpate pages, nor can new pages be loaded with javascript. This is a crit
Summary: There is no direct replacement for a frameset. This supports some functional...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
: 9054 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-17 20:57 UTC by contributor
Modified: 2010-10-04 14:33 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-02-17 20:57:33 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#non-conforming-features

Comment:
There is no direct replacement for a frameset.	This supports some
functionality and features that can't be emulated 100% by other methods. 
Server side includes cannot dynamically udpate pages, nor can new pages be
loaded with javascript.  This is a critical feature to keep or find a suitable
replacement.

Posted from: 208.48.138.218
Comment 1 Ms2ger 2010-02-18 19:17:01 UTC 
*** Bug 9054 has been marked as a duplicate of this bug. ***
Comment 2 Ian 'Hixie' Hickson 2010-02-25 06:33:24 UTC 
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.html

Status: Rejected
Change Description: no spec change
Rationale: I disagree that it is critical, but in any case all the important stuff can be done with CSS and <iframe>s, and the remainder can be done with scripting.