Re: [w3c/webcomponents] Custom pseudo-classes for host elements via shadow roots (:state) (#738)

We need to decide this based on use cases instead of rather subjective idea of how things should be organized conceptually.

During F2F, someone did raise a use case of such a state on an element with a shadow root that is not a custom element. I think the question really here is whether it's more common scenario to use this state with a custom element or with a shadow tree.

It seems that adding this capability to `ShadowRoot` is safer option of the two in the sense that if someone writing a custom element wanted to use a state, they can always attach a *trivial* shadow root which consists of a single slot element whereas a someone attaching a shadow root on a builtin element instead of a custom element doesn't have any workaround available to them.

-- 
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/738#issuecomment-488143551