Re: [w3c/webcomponents] Should custom elements be adoptable if so, how? (#512)

(I would expect Gecko to simply clone the document.)

The Fourth Proposal(tm) is that by default custom elements downgrade, then maybe upgrade, per your definitions. However, if custom elements have a `adoptedCallback` (to be introduced at a later stage), they would not be downgraded (or proto-swizzled) and remain the same object.

Any proto-swizzling for nodes remains its own issue (except that with the `adoptedCallback` code path it would be up to the author-defined custom element to do that kind of thing).

So overall it's no different from the "Downgrade, then maybe upgrade" proposal, except that the future story is a little different (and better, imo).

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