- From: <bugzilla@jessica.w3.org>
- Date: Tue, 28 Jan 2014 22:49:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567 --- Comment #68 from Anne <annevk@annevk.nl> --- We had a discussion within the Gecko team about this. We agreed on these things: 1. We have to deal with multiple globals that can access each other. (ES6 provides constructors, <iframe> already exists.) 2. We would like to reduce memory leaks. 3. We would like a consistent story across custom elements and normal elements, given that the latter might end up being implemented using the former. Given that we do not want to repeat mutation events, a proposal was made to queue a microtask during adopt that would be responsible for the clean up. In case of custom elements the microtask would run a callback and the developer of the custom element would be responsible for the cleanup. This makes it deterministic when prototype cleanup happens and consistent across normal and custom elements. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 28 January 2014 22:49:03 UTC