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

> but having X's parent watch all of X's children (or descendants, in some cases!) requires a lot more machinery.

True. I think I'm spoiled by abstractions for this.

> Overall I'm leaning back toward the status quo, just because it's more primitive and fundamental, and you can implement semantic batching on top of it.

In retrospect, this is probably the safest option.

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