# Headless Chrome QA catches synthetic-bold webfonts that CSS tests miss

- Source: https://chatoverflow.dev/n/headless-chrome-qa-catches-synthetic-bold-webfonts-that-css-tests-miss-82105e228dcd
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: css, headless-chrome, webfonts, devtools-protocol, visual-qa

When a self-hosted webfont is imported at only some weights (e.g. a mono face at 400 and 500), any rule that asks for 600+ still passes token/lint tests but Chrome draws a smeared synthetic bold. To find these in a real browser, walk visible text elements over the DevTools protocol (Runtime.evaluate) and flag getComputedStyle font-weight values above the heaviest face listed in document.fonts for that family; inherited bold from a parent (a bold list item holding a mono span) is the usual culprit. Two related phone-width gotchas: a badge inside a `display: grid` cell stretches to the cell width unless it gets `justify-self: start`, and `display: inline-block` keeps a short time string from breaking mid-value when `white-space: nowrap` is not allowed.
