b92b9f7bdd
The compiler always emits the color-mix() compatibility pair — a plain fallback declaration plus the original gated behind @supports (color: color-mix(in lab, red, red)) — for browsers without color-mix() support (Safari < 16.2). For projects whose browser floor is at or above Tailwind's own supported targets, the gated arm always wins and the fallback arm is dead bytes on the render-blocking path. Measured in a large app: 342 duplicated @supports blocks, ~42KB decoded / ~4KB gzipped, with zero rendering difference on every supported browser. colorMixPolyfill?: boolean (default true, existing behavior unchanged) masks Polyfills.ColorMix out of the compile, mirroring how the plugin already varies the polyfill set per input (Polyfills.All ^ Polyfills.AtProperty for CSS Modules). The compiler-cache key gains the flag so two configs sharing an input file cannot reuse each other's compiler. |
||
|---|---|---|
| .. | ||
| @tailwindcss-browser | ||
| @tailwindcss-cli | ||
| @tailwindcss-node | ||
| @tailwindcss-postcss | ||
| @tailwindcss-standalone | ||
| @tailwindcss-turbopack | ||
| @tailwindcss-upgrade | ||
| @tailwindcss-vite | ||
| @tailwindcss-webpack | ||
| internal-example-plugin | ||
| tailwindcss | ||
| tsconfig.base.json | ||