This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22991 - [Custom]: Elaborate enqueuing a lifecycle callback
Summary: [Custom]: Elaborate enqueuing a lifecycle callback
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14968
  Show dependency treegraph
 
Reported: 2013-08-17 01:31 UTC by Dominic Cooney
Modified: 2013-08-26 18:50 UTC (History)
0 users

See Also:


Attachments

Description Dominic Cooney 2013-08-17 01:31:52 UTC
There are some conditions I think are missing. These are probably in other open bugs but here's a summary:

- Inserted, removed need to become entered, left document; they should only be enqueued if the document has a view.
- The entered callback should be queued at the point the prototype changes, and not when the created callback is scheduled.
- With the exception of the created callback and the magic entered callback, callbacks should not be queued until the created callback starts to run.
- There's this newfangled "not dispatching while the created callback is running."
Comment 1 Dimitri Glazkov 2013-08-26 18:50:40 UTC
(In reply to comment #0)
> There are some conditions I think are missing. These are probably in other
> open bugs but here's a summary:
> 
> - Inserted, removed need to become entered, left document; they should only
> be enqueued if the document has a view.

https://dvcs.w3.org/hg/webcomponents/rev/3d4a6a4e4a3d and bug 22565.

> - The entered callback should be queued at the point the prototype changes,
> and not when the created callback is scheduled.

https://dvcs.w3.org/hg/webcomponents/rev/81123e455a55

> - With the exception of the created callback and the magic entered callback,
> callbacks should not be queued until the created callback starts to run.
> - There's this newfangled "not dispatching while the created callback is
> running."

I'll lump both of these into bug 22966.