- From: <bugzilla@jessica.w3.org>
- Date: Tue, 25 Jun 2013 17:05:03 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22446 --- Comment #1 from Dimitri Glazkov <dglazkov@chromium.org> --- (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. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 25 June 2013 17:05:05 UTC