commit 7b56e84e53f50611726927b02a6468776ab318c5
parent 6df3183859c6e0b860892253d37ada156063e6d9
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Sat, 26 Sep 2026 00:11:54 -0400
common: the geometricPrecision comment says why Plex hints on Linux (gasp grid-fitting, no TrueType instructions) and why the scope starts at 1.5x (brand S3)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Diffstat:
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/common/styles/tokens.css b/common/styles/tokens.css
@@ -125,19 +125,19 @@
font-stretch: 112%;
}
-/* Fractional glyph advances. IBM Plex Sans ships TrueType hinting, and
- Chromium on Linux (FreeType) applies it at a device pixel ratio of 2 and
- up, rounding each advance to a whole CSS pixel: at 14px the `g` of "Light"
- or "Signal" measured 9px against its 7.41px design width, which read as
- "Lig ht" and "Sig nal". geometricPrecision turns hinting off and lays text
- out at the design widths. It changes nothing where text is not hinted
- (macOS, iOS, Android's subpixel layout). Form controls are named too: the
- UA sheet resets their text-rendering to auto, so a button's "Results" would
- still read "Res ults".
- Scoped to 1.5dppx and up, where the gaps are. Below it the advances are
- still whole pixels, but the hinted glyph fills them: "Signal" reads clean at
- 1x and 1.25x and splits from 1.5x (150 % and 175 % desktop scaling too), so
- 1x Linux and Windows screens keep the hinting that makes 11–14px text crisp. */
+/* Fractional glyph advances. IBM Plex Sans, as Google Fonts serves it, has no
+ TrueType instructions but a `gasp` table that asks for grid-fitting at every
+ size, so FreeType hints it on Linux and Chromium rounds each advance to a
+ whole CSS pixel: at 14px the `g` of "Light" or "Signal" is 9px against its
+ 7.41px design width, at every device pixel ratio. At 1x and 1.25x the hinted
+ glyph fills that advance; from 1.5x up (150 % and 175 % desktop scaling
+ too) it is drawn finer than it is spaced, and the words read "Lig ht" and
+ "Sig nal". geometricPrecision turns hinting off and lays text out at the
+ design widths, so it is scoped to 1.5dppx and up, and 1x screens keep the
+ hinting that makes 11–14px text crisp. It changes nothing where text is not
+ hinted (macOS, iOS, Android's subpixel layout). Form controls are named
+ too: the UA sheet resets their text-rendering to auto, so a button's
+ "Results" would still read "Res ults". */
@media (min-resolution: 1.5dppx) {
html,
button,