You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I compared with v3.4.17 and the order was the above, so I guess this is a regression right?
Just to explain our use case: we have a large code base and we didn't want to apply the following text-black dark:text-gray-200 everytime we were using text-black. So for some text-* or bg-* colors we override it at the global level by doing this:
Hey! I understand that you're frustrated with this change but as @adamwathan mentioned in the discussion (#16070), this is an expected side-effect of Tailwind CSS 4 moving to layers. I'm going to close this issue and respond on the GitHub discussion with some more detail.
What version of Tailwind CSS are you using?
For example: v4.0.1
What version of Node.js are you using?
For example: v22.1
What browser are you using?
All major browsers
What operating system are you using?
macOS
Reproduction URL
Bug reproduction link: https://play.tailwindcss.com/oTvhvobEoO?file=css
Describe your issue
Following up on #16068
Sorry I think my last issue was not explicit enough.
I posted a new reproduction link to demonstrate the issue: https://play.tailwindcss.com/oTvhvobEoO?file=css
I think there is an issue with the generated css order:
But I believe the order should be this one:
I compared with v3.4.17 and the order was the above, so I guess this is a regression right?
Just to explain our use case: we have a large code base and we didn't want to apply the following
text-black dark:text-gray-200
everytime we were usingtext-black
. So for sometext-*
orbg-*
colors we override it at the global level by doing this:But still in some cases we'd like to have the option to override it with another color (e.g
text-black dark:text-blue
)The options you suggested here are not really what we expect since it will affect global colors
Let me know if I can clarify more 👍
The text was updated successfully, but these errors were encountered: