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

> > I disagree. If we picked the behavior WebKit/Blink uses which is to keeping the original prototype and pull the definition from the old window, then custom elements will continue to function and appears to behave identically to builtin elements.
>
> Do you think it would be acceptable to spec this behavior for custom elements (just like it is currently specced for built-in elements), despite Firefox not following the spec for built-in elements? Or do you think it's only OK to spec a useful behavior for custom elements if Firefox first changes its behavior for built-in elements to follow the current spec?

I don't think it's acceptable to be specifying this behavior for custom elements without reaching a consensus on what happens to adopted builtin elements unless we delegate the entire work to authors e.g. by simply calling `adoptedCallback` and not doing anything in UA.

However, I would be surprised if @bzbarsky and others at Mozilla are okay with that kind of behavior since that would mean that all custom elements adopted into another document would leak the original document if they're not okay with leaking the original owner document of builtin 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/512#issuecomment-223739193