24017 2013-12-06 06:02:41 +0000 template is not in ancestor chain for template contents in "Parsing HTML fragments" algorithm 2013-12-10 22:50:27 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All RESOLVED FIXED P2 normal Unsorted 1 wchen ian ian mike rafaelw rniwa contributor oldest_to_newest 97230 0 wchen 2013-12-06 06:02:41 +0000 http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#parsing-html-fragments In the "Parsing HTML fragments" step 4, sub-step 7, it says: "[...] (If there is no such form element, or if there's a template element in the ancestor chain, the form element pointer keeps its initial value, null.)" It looks like the intent is to make sure that the form pointer is null for descendents of template contents. However, the ancestor chain of those descendents will not contain the hosting template element. It will contain the the template content document fragment (at the root). 97258 1 ian 2013-12-06 18:28:07 +0000 Hm. I guess there's no way to know from just looking at a node whether or not the node is template contents, huh. I wonder how to fix this. 97262 2 wchen 2013-12-06 18:35:33 +0000 (In reply to Ian 'Hixie' Hickson from comment #1) > Hm. I guess there's no way to know from just looking at a node whether or > not the node is template contents, huh. I wonder how to fix this. You can get to the template content document fragment by walking up to the root and you can check the host (http://dom.spec.whatwg.org/#concept-documentfragment-host) to see if it is a template element. 97263 3 ian 2013-12-06 18:46:55 +0000 Ah, interesting. Thanks. 97354 4 ian 2013-12-09 21:17:28 +0000 On further reflection, I removed the special-casing of <template> there. It doesn't make any sense if you think about it, because if the innerHTML contents _do_ include a <form>, the form element pointer gets set and everything — the parser logic doesn't know it's in a template there. This does mean we're in a weird spot here, where this: <form><template><form><form> ...parses differently than the similar case where a <template> element's contents are set to "<form><form>" using innerHTML. 97427 5 contributor 2013-12-10 22:50:06 +0000 Checked in as WHATWG revision r8337. Check-in comment: innerHTML on template contents works like outside templates, when it comes to forms. http://html5.org/tools/web-apps-tracker?from=8336&to=8337