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

> For custom elements my thought was that we would not take an opinion on this question.

I don't think we can decide what custom elements do without agreeing on what regular elements should do.

> Adopting should downgrade an element's status to "undefined" (so :defined doesn't match it and no callbacks fire anymore)

That doesn't make any sense to me.  An element doesn't suddenly get un-created just because it got inserted into a new document.  e.g. an input element that gets adopted into a new document preserves the dirty value ([see demo](https://jsfiddle.net/k1horvft/)).

Also, calling different constructors twice on the same element seems like an abuse.


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