Skip to content

"rotate-0" CSS different between "dev" and "build" #17915

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

Closed
ZebraNorth opened this issue May 7, 2025 · 2 comments
Closed

"rotate-0" CSS different between "dev" and "build" #17915

ZebraNorth opened this issue May 7, 2025 · 2 comments
Labels

Comments

@ZebraNorth
Copy link

What version of Tailwind CSS are you using?

v4.1.5

What build tool (or framework if it abstracts the build tool) are you using?

Vite 6.3.5

What version of Node.js are you using?

v22.13.1

What browser are you using?

Chrome

What operating system are you using?

Windows

Reproduction URL

https://play.tailwindcss.com/zpabWAazWw

Describe your issue

When running npm run dev the rotate-0 class is compiled as rotate: 0deg.
When running npm run build it is compiled as rotate: none.

These are not equivalent, as 0deg will create a new stacking context but none will not. This causes the order of the divs in reproduction above to be swapped depending on whether you run dev or build.

@ZebraNorth ZebraNorth changed the title CSS different between "dev" and "build" "rotate-0" CSS different between "dev" and "build" May 7, 2025
@philipp-spiess
Copy link
Member

philipp-spiess commented May 7, 2025

Seems like an issue in lightningcss. Mind filing an upstream bug report?

If your intention is to create a new stacking context, I'd suggest you use the isolation utility to be more explicit!

@ZebraNorth
Copy link
Author

Seems like an issue in lightningcss. Mind filing an upstream bug report?

If your intention is to create a new stacking context, I'd suggest you use the isolation utility to be more explicit!

Thanks! I did consider isolation but I wasn't sure if it was the right tool for the job or not.

I'll close this ticket, as it's an upstream problem.

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

No branches or pull requests

2 participants