Re: [w3c/webcomponents] The custom element state when constructor thrown (#533)

I agree with @rniwa that we shouldn't run constructor mulitple times on the same element.

One more thing we need to take care of, if we were to add a new state, is that whether the new state is [defined] or not. Semantically, it is not _defined_. However, the expected most common use case of _defined_ is `not(:defined)` to find elements yet to be upgraded, as in the example in [element definition]. From this purpose, I would like it to be _defined_.

I mildly prefer it be _defined_ for the reason above, but I'm ok either way.

And if we were to make it as _defined_, we could use _uncustomized_ too. I'm ok either way on this too.

[defined]: https://dom.spec.whatwg.org/#concept-element-defined
[element definition]: https://html.spec.whatwg.org/multipage/scripting.html#element-definition

---
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/533#issuecomment-232247988