[Webkit-unassigned] [Bug 188284] Custom elements created by the parser in a connected position have their constructors and connectedCallbacks called out of order

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Aug 5 00:44:47 PDT 2018


https://bugs.webkit.org/show_bug.cgi?id=188284

Frédéric Wang (:fredw) <fred.wang at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fred.wang at free.fr

--- Comment #3 from Frédéric Wang (:fredw) <fred.wang at free.fr> ---
For the synchronous case ('in-document HTML'), the patch on bug 188190 is supposed to force execution of the connectedCallBack immediately after insertion of the element (There is WPT test to ensure the element is indeed empty when connectedCallBack is called). That might improve things, but I don't know beforehand what we do regarding the order of constructor call / element insertion, especially since HTMLConstructionSite uses an m_taskQueue to delay insertion.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180805/ea6025a6/attachment.html>


More information about the webkit-unassigned mailing list