22486 2013-06-26 23:16:30 +0000 [HTML Template Element] Should we just remove support for <frameset>/<frame> 2016-04-25 23:17:52 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC All RESOLVED FIXED whatwg-resolved P2 normal --- 1 rafaelw dave.null adamk annevk dglazkov hsivonen ian jackalmage mike public-html-admin public-html-wg-issue-tracking travil tross wchen public-html-bugzilla oldest_to_newest 89932 0 rafaelw 2013-06-26 23:16:30 +0000 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? 89933 1 ian 2013-06-26 23:26:39 +0000 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). 89934 2 jackalmage 2013-06-26 23:58:15 +0000 I see no problem with nuking it. Nobody should be using <frameset> anyway. 89980 3 adamk 2013-06-27 21:28:36 +0000 I'm surprised to hear <template><frameset> was even allowed before, so I'm happy to get rid of it. 126138 4 travil 2016-04-25 23:17:52 +0000 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!