Upgrading Tailwind from 4.3.2 to 4.3.3 changed our application’s typography and text metrics.
The default changed from:
ui-sans-serif, system-ui, sans-serif
to:
-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", "Noto Sans", Arial, sans-serif
This was intended to fix CJK language handling on Windows, but also changes Latin typography, wrapping, and layout depending on locally installed fonts.
The change is documented under “Fixed” in the 4.3.3 release notes (https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.3.3), despite being visually breaking. The font-family documentation (https://tailwindcss.com/docs/font-family) still shows the previous default stack.
Tailwind previously stated that Preflight follows semantic versioning and should not change incompatibly within a major version in this maintainer discussion (#7496). Shipping a global typography change in a patch release appears inconsistent with that expectation.
Upgrading Tailwind from 4.3.2 to 4.3.3 changed our application’s typography and text metrics.
The default changed from:
ui-sans-serif, system-ui, sans-serif
to:
-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", "Noto Sans", Arial, sans-serif
This was intended to fix CJK language handling on Windows, but also changes Latin typography, wrapping, and layout depending on locally installed fonts.
The change is documented under “Fixed” in the 4.3.3 release notes (https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.3.3), despite being visually breaking. The font-family documentation (https://tailwindcss.com/docs/font-family) still shows the previous default stack.
Tailwind previously stated that Preflight follows semantic versioning and should not change incompatibly within a major version in this maintainer discussion (#7496). Shipping a global typography change in a patch release appears inconsistent with that expectation.