Re: [w3c/webcomponents] Interface/class-based selector (#719)

Right, (1) seems pretty bad, I think we can reject that out of hand.

For the specific use-case in this thread, the subclassing isn't mutable JS state at all, right? It's defined when you call `.defineElement()` and can't change afterwards (or if it can, it's from some unregister() method that I'm not remembering off the top of my head).  If that's the case, keying a CSS pseudo-class off of this seems totally reasonable. Maybe call it `:subclass-of(<type-selector>)`?

-- 
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/719#issuecomment-367143705