21825 2013-04-25 08:38:30 +0000 [Custom]: Specify or comment on node adoption--does element initialization happen? 2013-06-19 17:02:48 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED DUPLICATE 20488 P2 normal --- 14968 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 86771 0 dominicc 2013-04-25 08:38:30 +0000 The spec speaks to createElement, createElementNS, and tree construction during parsing. But DOM operations such as cloneNode, appendChild, adoptNode, etc. also create elements. Custom Elements should specify when lifecycle callbacks run in these cases. If they don't run (assumed, given the status quo) some commentary about which DOM operations *won't* trigger lifecycle events would be useful to guide implementations and authors. 88024 1 dglazkov 2013-05-21 21:28:02 +0000 I am probably reading this wrong, but don't we only create new elements in cloneNode? I don't think appendChild or adoptNode do that. 88888 2 dominicc 2013-06-07 04:34:51 +0000 (In reply to comment #1) > I am probably reading this wrong, but don't we only create new elements in > cloneNode? I don't think appendChild or adoptNode do that. Ah... in legacy DOM appendChild may fall back to adoptNode if the node is in a different document, and adoptNode may fall back to doing importNode depending on implementations, and importNode creates an element. In DOM4 it looks like that adoptNode->importNode fallback does not exist. Great. But we need to handle cloneNode and importNode. In fact, DOM4 has a concept for "clone" <http://dom.spec.whatwg.org/#concept-node-clone> 89590 3 dglazkov 2013-06-19 17:02:48 +0000 Okay, then this is all bug 20488. *** This bug has been marked as a duplicate of bug 20488 ***