16873 2012-04-27 14:43:22 +0000 [Explainer]: Template inertness is not described sufficiently 2013-05-29 11:52:59 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED FIXED P2 normal --- 14949 1 james dominicc dominicc public-webapps-bugzilla oldest_to_newest 67142 0 james 2012-04-27 14:43:22 +0000 "Appending inert DOM to a document node makes it go "live", as if the DOM tree was just parsed from markup (setting innerHTML)." This doesn't make much sense. Presumably appendChild won't serialize + reparse the contents. Possibly you mean some of the state flags will be reset? In general for items with state e.g. script it's not clear what will happen to the state when the node is in a <template> and what will happen when it is moved outside the template. 67275 1 dglazkov 2012-05-02 23:27:47 +0000 Can you help me understand which part doesn't make sense? As far as describing the effect, it seems the sentence is ok. Are you looking for a more detailed explanation of what happens? I could probably add a summary of template insertion algorithm from http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#dfn-template-insertion-algorithm. 88375 2 dominicc 2013-05-29 11:52:59 +0000 I changed the explanation in the explainer in <https://dvcs.w3.org/hg/webcomponents/rev/33914fc2661a>