24866 2014-02-28 18:23:40 +0000 [Custom]: Consider adding inserted/removed callback 2015-07-06 08:06:11 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED MOVED P2 normal --- 14968 1 dglazkov dglazkov annevk dominicc mike public-webapps sjmiles wchen public-webapps-bugzilla oldest_to_newest 101642 0 dglazkov 2014-02-28 18:23:40 +0000 These will be mapped exactly to inserted/removed hooks in DOM core: * http://dom.spec.whatwg.org/#node-is-inserted * http://dom.spec.whatwg.org/#node-is-removed Based on discussion in bug 24314, we could even deprecate attached/detached callback in their favor. 101648 1 sjmiles 2014-02-28 19:03:17 +0000 It's definitely appealing to expose DOM core with high fidelity, but we have some performance realities that concern me. In particular, calling back into JS from the native side is known to expensive (at least on some platforms). The currently spec'd callback is only called when an element's subtree is attached or detached form the main document, which is a much lower frequency situation. This is less powerful, but it is perhaps a good tradeoff to avoid killing custom elements with expensive callbacks? 102447 2 annevk 2014-03-17 12:18:02 +0000 Note that the callbacks in DOM need to be updated to take several arguments to provide context for what actually happened. I haven't attempted that rewrite yet. 121652 3 hayato 2015-07-06 08:06:11 +0000 Moved to https://github.com/w3c/webcomponents/issues/222