- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Jun 2013 02:36:22 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22288 Bug ID: 22288 Summary: [Custom]: A set of methods should invoke lifecycle callbacks Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: dominicc@chromium.org QA Contact: public-webapps-bugzilla@w3.org Blocks: 14968 There is a jsbin <http://jsbin.com/arizup/2/edit> which illustrates that this author expects the ready, inserted and removed callbacks to be invoked synchronously. However the spec as written says these are run at a microtask checkpoint. Implementers are often concerned about adding synchronous callbacks in response to DOM modifications because of difficulties with Mutation Events. In theory their concerns can be addressed by treating modifications arising from script operations and modifications arising from parsing differently. The precise timing of the callbacks can be not during the tree modification itself, but when control is about to return to script (so the UA is "running script anyway" at approximately that point.) For example, in the jsbin case above, the call to node.remove could run lifecycle events after the UA has modified the DOM, but before execution returns to the script engine. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 6 June 2013 02:36:24 UTC