Re: [w3c/webcomponents] [IDEA] deferred upgrade for Custom Elements. (#559)

@rniwa 

> I think this problem also goes away if we [add back `childrenChangedCallback`](https://github.com/w3c/webcomponents/issues/550).

Also, which criteria would cause a `childrenChangedCallback` to fire? f.e. when a child is connected, disconnected, upgraded. Anything else? An attribute change could be considered a change. Maybe it is better to make specific callbacks for specific changes. f.e. `childUpgradedCallback`, `childConnectedCallback`, `childDisconnectedCallback`, `childAttributeChangedCallback` (this is is questionable, but may nonetheless be helpful in some cases), etc.

-- 
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/559#issuecomment-243937985