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

State Variants Priority Order #392

Closed
fedetibaldo opened this issue Feb 20, 2018 · 3 comments
Closed

State Variants Priority Order #392

fedetibaldo opened this issue Feb 20, 2018 · 3 comments

Comments

@fedetibaldo
Copy link
Contributor

Foreword

People are (or at least, I am) increasingly excited about the possibility of having everything they need out of the box thanks to Tailwind, and state variants are a vital part of building user interfaces.
Tailwind already supports a bunch of them, but new ones are always proposed and discussed (see #136) and, as time goes on, they may get introduced as well.

Purpose

There is a problem though: since Tailwind does not rely on !important
rules to override styles, the output order of the state variants becomes crucially important.
It's true: users may tailor their code by implementing priorities by themselves and fit their needs!
Good defaults, however, could save a lot of headaches and work.

That's what this thread is for: discuss better state variants priorities.

@fedetibaldo
Copy link
Contributor Author

Hover vs. Focus

Currently, hover has a higher priority than focus. However, as discussed in the PR #379, this choice has his pros and cons.
As it is now, buttons have huge benefits, whilst inputs may lack consistency.

Are you relying on or fighting against this order?

@adamwathan
Copy link
Member

Sorted out for 0.5.0 👍

@fedetibaldo
Copy link
Contributor Author

Nice! I've been really looking forward for this change

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

2 participants