22446 2013-06-25 07:06:53 +0000 [Custom]: Commentary about lifecycle callbacks queue being empty when document.register is invoked is incorrect 2013-06-25 20:48:08 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC Linux RESOLVED DUPLICATE 22459 P2 normal --- 14968 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 89787 0 dominicc 2013-06-25 07:06:53 +0000 The spec has this informative language: "Also, because of when lifecycle callbacks are added to the lifecycle callbacks queue, the queue should be empty when document.register is invoked." I don't think it is true; consider this case: <script> var A = document.register('x-a', ...); // callbacks have been exhaustively invoked by register() at this point var x = new A(); // ready has been eagerly invoked by the constructor at this point document.body.appendChild(x); // inserted(x) is queued at this point // queue is NOT empty document.register('x-b', ...); </script> 89823 1 dglazkov 2013-06-25 17:05:03 +0000 (In reply to comment #0) > The spec has this informative language: > > "Also, because of when lifecycle callbacks are added to the lifecycle > callbacks queue, the queue should be empty when document.register is > invoked." > > I don't think it is true; consider this case: > > <script> > var A = document.register('x-a', ...); > // callbacks have been exhaustively invoked by register() at this point > var x = new A(); > // ready has been eagerly invoked by the constructor at this point > document.body.appendChild(x); > // inserted(x) is queued at this point > // queue is NOT empty The thing is, this is where developer will expect the inserted to fire. We need to figure out what this means from spect/impl perspective. 89849 2 dglazkov 2013-06-25 20:48:08 +0000 *** This bug has been marked as a duplicate of bug 22459 ***