20438 2012-12-19 00:09:51 +0000 [Custom]: consider adding "inserted" and "removed" lifecycle methods 2013-05-08 16:51:37 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED DUPLICATE 21660 P2 normal --- 18511 1 jmesserly dglazkov sjmiles public-webapps-bugzilla oldest_to_newest 80381 0 jmesserly 2012-12-19 00:09:51 +0000 If a component author needs to register an event on something other than their own shadow dom tree (perhaps something global accessed from window, or more likely Object.observe on a JS object), they need a way to unregister the handler so it doesn't leak the handler. Many of the popular web frameworks have some sort of "destory"/"disposable"/"removed" mechanism to help deal with this. 80382 1 sjmiles 2012-12-19 00:17:41 +0000 Yes, we have encountered this issue also. To avoid dangling references, a component needs to know when it's inserted/removed from DOM. Perhaps an event when parentNode changes? 87429 2 dglazkov 2013-05-08 16:51:37 +0000 *** This bug has been marked as a duplicate of bug 21660 ***