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

Hmm. I think it would be better to be not defined. After all, it will not work like a defined element would. It has not yet been upgraded (and never will be). `:not(:defined)` would be better off matching it, I think. For example if people are trying to hide elements until they are interactive.

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