Skip to content
This repository has been archived by the owner on May 28, 2024. It is now read-only.

Should built-in states be reflected in the API #10

Open
plinss opened this issue May 23, 2020 · 1 comment
Open

Should built-in states be reflected in the API #10

plinss opened this issue May 23, 2020 · 1 comment

Comments

@plinss
Copy link

plinss commented May 23, 2020

Given the change in syntax, and that all custom states now have to be prefixed with '--', it raises the question of whether built-in states should also be reflected in the API.

e.g. if an element is being hovered over, should el.states.has('hover') be true?

This fits with Houdini's mission to explain existing CSS behavior.

Of course, the user should no be able to add or clear built-in state.

@tkent-google
Copy link
Collaborator

Yeah, we can extend the feature for existing built-in pseudo classes.

WICG/webcomponents#813

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants