This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16873 - [Explainer]: Template inertness is not described sufficiently
Summary: [Explainer]: Template inertness is not described sufficiently
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Dominic Cooney
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14949
  Show dependency treegraph
 
Reported: 2012-04-27 14:43 UTC by James Graham
Modified: 2013-05-29 11:52 UTC (History)
1 user (show)

See Also:


Attachments

Description James Graham 2012-04-27 14:43:22 UTC
"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.
Comment 1 Dimitri Glazkov 2012-05-02 23:27:47 UTC
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.
Comment 2 Dominic Cooney 2013-05-29 11:52:59 UTC
I changed the explanation in the explainer in <https://dvcs.w3.org/hg/webcomponents/rev/33914fc2661a>