- From: <bugzilla@jessica.w3.org>
- Date: Wed, 08 May 2013 03:51:46 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21962 Bug ID: 21962 Summary: [Custom]: Running lifecycle callbacks should be integrated with microtask processing 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 This language should be revised: "In addition, just before the user agent is to perform a microtask checkpoint, the user agent must invoke lifecycle callbacks for the unit of related similar-origin browsing contexts to which the scripts' browsing context belongs." Consider the case where a MutationObserver callback does something that causes a lifecycle callback to be enqueued. That lifecycle callback may never be delivered. Maybe the HTML5 microtask needs to be teased apart into conditions to run until a fixed point and the operations to run? For safety in Blink I'm tempted to drop lifecycle callbacks enqueued in a MutationObserver on the floor. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 8 May 2013 03:51:47 UTC