- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Dec 2012 00:09:51 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20438 Bug ID: 20438 Summary: [Custom]: consider adding "inserted" and "removed" lifecycle methods Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: jmesserly@google.com QA Contact: public-webapps-bugzilla@w3.org Blocks: 14968 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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 19 December 2012 00:09:52 UTC