chore(deps): bump @tailwindcss/vite from 4.3.2 to 4.3.3 in /extension

[dependabot]

Bumps @tailwindcss/vite from 4.3.2 to 4.3.3.

Release notes

Sourced from @​tailwindcss/vite's releases.

v4.3.3

Fixed

• Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#20297)
• Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#20298)
• Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#20292)
• Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#20299)
• Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#20302)
• Parse selectors like [data-foo]div as two selectors instead of one (#20303)
• Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)
• Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#20124)
• Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#20314)
• Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#20319)
• Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#20325)
• Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#20318)
• Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#20329)
• Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#20335)
• Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)

Changelog

Sourced from @​tailwindcss/vite's changelog.

[4.3.3] - 2026-07-16

Fixed

• Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#20297)
• Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#20298)
• Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#20292)
• Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#20299)
• Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#20302)
• Parse selectors like [data-foo]div as two selectors instead of one (#20303)
• Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)
• Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#20124)
• Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#20314)
• Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#20319)
• Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#20325)
• Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#20318)
• Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#20329)
• Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#20335)
• Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)

Commits

• c2b24dd 4.3.3 (#20334)
• bdcd708 Don't trigger a full page reload for scanned files that Vite processes as mod...
• See full diff in compare view

[dependabot]

Labels

The following labels could not be found: dependencies, extension. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[vineethkrishnan]

Verified in a clean-room build. Safe to merge, high confidence.

Note on method: the playwright suite in this repo drives the web SPA and there is no harness that loads the extension, so it cannot exercise an extension-only bump. What settles a CSS-toolchain patch is whether the emitted stylesheet changes, so I compared the build output directly.

Both sides built from clean git worktree checkouts with no pre-existing node_modules, this PR head (already rebased on current main) against main:

Job passes end to end

npm ci / npm run typecheck / npm test (7 files, 74 tests) / build chrome / build firefox

Emitted popup CSS is functionally identical. 402 rules, 401 byte-identical. The single difference:

-  --tw-translate-y:0
+  --tw-translate-y:0px

0 and 0px are equivalent as a <length>, and the rule is .disabled:hover:translate-y-0, a disabled-state hover reset. Cosmetic codegen change, no rendering effect.

Everything else is byte-identical. The popup JS chunk is identical once the CSS filename reference is normalised (both 368868 bytes); popup.html differs only in the two content-hash filenames it points at.

Supporting evidence: the identical plugin version is already on main for the web app via #326, and the full playwright e2e suite passed there.

This also clears the version skew left by #321 merging alone: tailwindcss is at 4.3.3 while @tailwindcss/vite still pins @tailwindcss/node@4.3.2 -> tailwindcss@4.3.2, so the tree currently carries both. Merging this resolves it.

The red "Validate PR Title" check is a GitHub Actions infrastructure flake from 2026-07-20 (No server is currently available to service your request), not a validation failure.

[vineethkrishnan]

Verified in a clean-room build: full job passes, and the emitted CSS is functionally identical to 4.3.2 (one 0 -> 0px codegen change on a disabled-state rule). Also clears the tailwind version skew left by #321.