This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Edge (soon) and Chrome will allow <template> in <frameset>, whereas the spec currently forces the tag to be ignored.
This sounds like a bad idea.
Filed https://code.google.com/p/chromium/issues/detail?id=528233 https://github.com/w3c/web-platform-tests/issues/2134
Anne, what is a bad idea and why? Do you have any context on why this changed when merging templates into HTML?
Probably best to ask Ian. Making <frameset> parsing more complicated doesn't seem worth the effort however.
I think Blink can change the behavior if the current spec is what we can agree on. I'd like to wait for the conclusion of this discussion.
<frameset> only allows <frameset>, <frame>, and <noframe>. The spec seems pretty clear about this. Without a really, really good reason I don't think we should change it.
In particular, since <frameset><script> drops the script, it seems most sensical to drop <template> also. Framesets are non-conforming so there's no use case.
OK, I've also filed a bug to remove Edge support for this scenario. Thanks all. (ref: VSO4512370)