Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Psuedo-classes should come after Psuedo-elements #3

Open
dfmcphee opened this issue Feb 22, 2016 · 0 comments
Open

Psuedo-classes should come after Psuedo-elements #3

dfmcphee opened this issue Feb 22, 2016 · 0 comments

Comments

@dfmcphee
Copy link
Contributor

I would argue that Psuedo-classes such as :hover, :active, and :focus (move these out of psuedo-classes and consider them psuedo-styles?) should come after Psuedo-elements (if not at the very end of our ordering). Example: often a psuedo-element will need to respond to the :hover of its parent. Isn't it more organized to wrap all of that up in a single declaration?

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

No branches or pull requests

1 participant