This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
+++ This bug was initially created as a clone of Bug #23002 +++ Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html Multipage: http://www.whatwg.org/C#the-after-head-insertion-mode Complete: http://www.whatwg.org/c#the-after-head-insertion-mode Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Hoist <template> to head? Posted from: 90.230.218.37 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.49 Safari/537.36 OPR/16.0.1196.45 (Edition Next)
Why? We can't really expand the set of in-<head> elements anyway, and with MDV, there are uses for inline templates.
(In reply to comment #1) > Why? See the comments in bug 23002. > We can't really expand the set of in-<head> elements anyway, and with > MDV, there are uses for inline templates. <template> is already allowed in <head>. That's not what this bug is about.
<template> is allowed in head and body. This bug is asking the question when it is placed after </head> but before <body>, which one does it get put into. Currently it's <body>, and Simon is saying it should be <head>
Tony and I chatted--initially we were alarmed by the title, but after reading the details this makes sense. I like the consistency that it then maintains between the other head-able elements. So, I'm in favor of making the change. Thanks for looping us in.
The fact that inline templates are intended to be used by MDV to stamp out DOM from a data source mans that hoisting is definitely not what we want to do. <template> isn't intended to be just a data-source element - it'll actually *do* something where it's placed if you put the right attributes on it.
Clarifying the title.
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: Accepted Change Description: Ported change from WHATWG spec