Re: [w3c/webcomponents] [idea] childConnectedCallback and childDisconnectedCallback (#550)

> I don't know if this is part of spec though, but IMO definitely not ideal because it shows some behavior that isn't a normal part of what people expect from JavaScript.

which is exactly my point since about ever: the most important piece of the puzzle to grant robust delivery of custom elements is not in the specifications and nobody knows, not even browser vendors, when an element can be trustfully initialized.

Yes, we can always add nodes after that, but the point is that nobody knows when it's even possible to do so.

We need to solve this part of the puzzle, or anything dealing with `<div>` and built-in extends would always feel like a better choice than this funny unknown that is custom elements upgrade.

As summary, we need an `upgradedCallback` or we can stop bothering with CE, IMO.



-- 
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/550#issuecomment-458078838