Re: [w3c/webcomponents] defineElement should not cache lifecycle callbacks and prototype of a custom element class (#417)

On Late binding of attributeChangedCallback by the user agent:
* We agree with Won't Fix because
  * It is entirely consistent with implementation principles, that the UA cache the “internal” behavior for a custom element. We are entirely in agreement with comment https://github.com/w3c/webcomponents/issues/417#issuecomment-204569197. 
  * Have a hard time understanding the use case for wanting the late binding (in particular, a custom element instance will always be created consistently first, before any of the lifecycle callbacks are invoked anyway. Conditional programming can be added to the lifecycle callbacks to workaround any limitations imposed by user agent’s caching them).
  * Makes it easier for web devs to reason about the behavior of all custom elements of a given class.
  * Are concerned about the performance impact of a late-binding for callbacks that could be invoked rather frequently (like attributeChangedCallback).


---
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/417#issuecomment-205533503