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 22486 - [HTML Template Element] Should we just remove support for <frameset>/<frame>
Summary: [HTML Template Element] Should we just remove support for <frameset>/<frame>
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard: whatwg-resolved
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-26 23:16 UTC by Rafael Weinstein
Modified: 2016-04-25 23:17 UTC (History)
12 users (show)

See Also:


Attachments

Description Rafael Weinstein 2013-06-26 23:16:30 UTC
Hixie points out at least once problem in it's behavior:

<template><frame><frameset> .. (can now never close the <frameset>

And <frameset> has been deprecated for quite some time.

I'm fine just removing it. I'd need to look to see what this would mean.

Opinions?
Comment 1 Ian 'Hixie' Hickson 2013-06-26 23:26:39 UTC
we should probably set frameset-ok to "not ok" when we see <template>, too, just to avoid the crazy stuff like <body><template></template><frameset> nuking the template while <body><template>x</template><frameset> doesn't (mind you, same thing happens with <body><p><frameset> vs <body><p>x<frameset>, so I'm not _too_ worried about this case).
Comment 2 Tab Atkins Jr. 2013-06-26 23:58:15 UTC
I see no problem with nuking it.  Nobody should be using <frameset> anyway.
Comment 3 Adam Klein 2013-06-27 21:28:36 UTC
I'm surprised to hear <template><frameset> was even allowed before, so I'm happy to get rid of it.
Comment 4 Travis Leithead [MSFT] 2016-04-25 23:17:52 UTC
HTML5.1 Bugzilla Bug Triage: Fixed (by prior WHATWG commit)

in template mode switches to frameset "not ok" causing it to be ignored.

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!