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

I agree with @MutationObserver here, `MutationObserves` is good enough for this very edge case. If you have many components with many children that need to be observed, you should probably look for alternative solutions, and question the viability of your current design when using WC APIs.

I don't think asking for child*Callback is realistic, specially because of its perf characteristics, which will probably force us to do something similar to the `observedAttributes`, which itself is very confusing and complicated.

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