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

When two custom elements are enqueued of connected callbacks, and the first `connectedCallback` removes the second one and inserts it back, whether `connectedCallback` is invoked during the removal or the insertion depends on the presence of `disconnectedCallback`.

This seems like a very unintuitive behavior for developers. Why should adding a `disconnectedCallback` which doesn't do anything change the timing at which `connectedCallback` is invoked?

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