Re: [w3c/webcomponents] Element.prototype.connectedCallback, et al. (#629)

If we're dealing *only* with custom elements, then putting `connectedCallback` on `Element.prototype` will work if the custom element calls `super.connectedCallback`.This means something like `childConnectedCallback`/`childDisconnectedCallback` can be implemented synchronously when the tree is entirely custom elements.

However, it won't work when the tree is mixed with native elements, because those never get `connectedCallback`/`disconnectedCallback` methods called.

There's probably other use cases for this.

Overall, the main point is that if those methods were called on native elements, it would be more inline with the Extensible Web Manifesto, it would explain native elements better, and it would mean that the above "monkey patching" works because the new APIs explain existing elements.

-- 
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/629#issuecomment-285902240