22991 2013-08-17 01:31:52 +0000 [Custom]: Elaborate enqueuing a lifecycle callback 2013-08-26 18:50:40 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 14968 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 92213 0 dominicc 2013-08-17 01:31:52 +0000 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." 92593 1 dglazkov 2013-08-26 18:50:40 +0000 (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.