Re: [w3c/webcomponents] A way to implement :hover, :active, etc, for custom elements. (#738)

> This is an API request to manually set :hover state on an element?

Yes, or something similar. Maybe custom states, similar to your `:part` idea but not tied to any particular element inside the custom element.

Maybe, for user land, something like `:state(some-state)`, in order to be separated from builtin states.

> How's this different from, e.g., changing a class or something like that?

That's changing the outside state that the user should define, whereas this feature would let outside user hook into inside-defined state. I think only outside user should define classes. Not to say it isn't possible to do it that way, but it doesn't feel as clean.

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