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

The problem in my last comment is because the elements are upgraded during DOM parsing, so an elements `connectedCallback` executes before the parser reaches the next element. When the parser is on an element can calls `connectedCallback`, `this.childNodes.length` of the currently-being-parsed-element is `0` even though in reality it will not be `0` a soon as the parser continues.

Making shareable reusable components currently involves tricky and difficult timing issues. Ideally it would be as easy as with React or Vue, so that anyone (especially newcomers to the web) can start making components without friction.

-- 
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-334988088