- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 01 Jul 2016 01:50:03 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
Received on Friday, 1 July 2016 08:50:32 UTC
> Which element definition is consulted for this opt-out? The source, I'd guess? Yes. > And you're not bothered by the fact that it runs two different constructors on the same element by default? And doesn't match built-ins? My assumption is that the typical "by default" is that you won't find a suitable definition in the other global. That it might upgrade is mostly a side effect of it being a custom element. The way to match built-ins is the `adoptedCallback` extension that allows for preserving identity and state, as well as any proto-swizzling may we reach agreement on that. All things I considered I think I prefer this over throwing, simply since throwing is such an unexpected behavior for these kind of operations. --- 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/512#issuecomment-229892899
Received on Friday, 1 July 2016 08:50:32 UTC