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

I _still_ think that a dedicated `childrenChangedCallback` or similar is needed to fix this very rough edge of the APIs, as requested in #550 and #619. The exact right combination of slotchange and and DOMContentLoaded events, MutationObserver, and `connectedCallback`, is just too obscure to be usable, and a `finishedParsingChildrenCallback` doesn't solve the dynamically changing children case.

The platform should provide a reasonable signal for "If I need to process children, when should I do 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-430670213