-
What version of Tailwind CSS are you using? v4.1.13 What build tool (or framework if it abstracts the build tool) are you using? postcss-loader 8.2.0 What version of Node.js are you using? v22.19.0 What browser are you using? Chrome What operating system are you using? macOS Reproduction URL https://play.tailwindcss.com/IryPEYKmlk?size=1254x807 Describe your issue At a viewport width of exactly 800px: This shows that arbitrary px values (min-[800px]) are always placed before named breakpoints like sm in the generated CSS, so the named breakpoint wins in the cascade. However, when using rem values (min-[50rem] = 800px), the arbitrary breakpoint appears after sm, so it correctly overrides. Steps to reproduce: Expected behavior: Actual behavior: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
There is some documentation that is related to this:
This extends to arbitrary breakpoints too. Thus, you should use the |
Beta Was this translation helpful? Give feedback.
There is some documentation that is related to this:
This extends to arbitrary breakpoints too. Thus, you should use the
50rem
version, or redefine your breakpoints aspx
values.