tailwindcss

mirror of https://github.com/tailwindlabs/tailwindcss.git synced 2025-12-08 21:36:08 +00:00

Go to file

Fix polyfill in combination with unused CSS variable removal (#17555 )

This PR fixes an issue we noticed while investigating #17553, where the
unused CSS variable removal didn't work properly when the theme variable
it tried to remove was modified by a polyfill rule.

The way the bookkeeping for the unused CSS variable worked was that it
tired to find the declaration inside it's parent after the traversal.
However, the `color-mix(…)` polyfill has since then made changes to the
declaration so it can't find it's position correctly anymore and will
thus instead delete the last declaration of the node (this caused
unrelated CSS variables to be eliminated while the ones with
`color-mix(…)` were unexpectedly kept).

To fix this, we decided to apply the polyfills after any eventual
deletions. This also ensures that no `@supports` query for the variables
are created and simplifies the code a bit since all polyfills are now
colocated.

## Test plan

- Added a unit test for the example we discovered in #17553
- Luckily the conditions of this seemed rare enough so that it doesn't
cause any other of our tests to update.

---------

Co-authored-by: Robin Malfait <malfait.robin@gmail.com>

2025-04-07 09:18:47 +00:00

.github

Watch CSS module files for changes (#17467 )

2025-03-31 18:44:06 +02:00

crates

Prepare v4.1.3 release (#17563 )

2025-04-04 19:54:23 +02:00

integrations

Vite: Don't register the current CSS file as a dependency on itself (#17533 )

2025-04-03 18:50:16 +02:00

packages

Fix polyfill in combination with unused CSS variable removal (#17555 )