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

Wouldn't it be an even better approach to create a `ComponentContentLoaded` event? That would solve the `attributeChangedCallback` as well, and it would make it so outside elements and components can attach a listener to that event (if they rely on it).

We could even have all components register at a central service in thei constructor on creation, and have that same service emit a global `ComponentsReady` event as soon as all registered components have emitted their `ComponentContentLoaded` event.

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