Re: [w3c/webcomponents] Custom Element definition ordering can cause difficult-to-find bugs. (#668)

@wiredearp 

> it sounds to me like the issue is actually fixed in the native implementation and that perhaps this appears worse than it really is because the polyfill uses Mutation Observers for some kind of asynchronous implementation?

All my observations were based on Chrome's native implementation: initial DOM parse not being atomic (connetedCallbacks fire from parent to child, down-the-tree, children visible _with_ deferral) while innerHTML being atomic (connectedCallbacks fire from child to parent, up-the-tree, children visible _without_ deferral).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/668#issuecomment-335284037