Re: [w3c/webcomponents] Presence of disconnectedCallback can expedite an invocation of connectedCallback (#760)

I think in most cases the parent should be handling the relationship with the children and not the other way around.

In the `picture` / `source` example, the `picture` would handle any child tree updates where a `source` was added or removed.

What is the `iframe` example you're thinking of @annevk?

Maybe there's room for something similar to the `adoptedCallback` where a callback is invoked when a custom element is re-parented? Or is it worth discussion the fact that maybe an element should have their `connected` / `disconnected` callbacks invoked if it's moved, but not if it's added / removed very quickly?

-- 
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/760#issuecomment-445577840