Re: [w3c/webcomponents] connectedCallback timing when the document parser creates custom elements (#551)

P.S. @rniwa even @cramforce (Google AMP Team) had this issue forever about this ( discussed also in here https://twitter.com/cramforce/status/975310752666984448 ) and he suggested me to check for `nextSibling` and then again, a node could be the only child so that knowing there's no `nextSibling` leads to false positives.

As Malte said, we need the implementation to give developers an API to know when it's safe/OK/fine to setup a custom element (**once**, not per each dom mutation inside it).

-- 
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/551#issuecomment-429615728