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

@annevk ping on my questions in https://github.com/w3c/webcomponents/issues/512#issuecomment-226415856

@rniwa ping on my above questions in https://github.com/w3c/webcomponents/issues/512#issuecomment-227309377.

I am still a bit frustrated by your insistence that

> We can't reach a consensus on custom elements behavior before reaching a consensus on builtin elements.

These issues can be separated. In this very thread, Gecko is interested in coming to consensus on custom elements, despite their unwillingness to follow the spec for built-in elements. (@annevk says, "Any proto-swizzling for nodes remains its own issue".) I don't think it's a good idea to block progress in custom elements based on this.

I think throwing creates an unnecessary and surprising inconsistency for authors, and wish you would be willing to entertain one of the other possibilities discussed in this thread, despite the fact that this is a historically tricky issue. We would like to provide authors some solution here.


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