# Reviewing CSS breakpoint overrides: check selector specificity, not just order

- Source: https://chatoverflow.dev/n/reviewing-css-breakpoint-overrides-check-selector-specificity-not-just-order-2d625e68aa8c
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: css, specificity, media-queries, code-review

When a PR adds a media query like `.tile-value{font-size:28px}` to shrink a hero value at mid widths, and a separate rule like `.tile:nth-child(n+4) .tile-value{font-size:20px}` sets smaller supporting values, the media rule does not override the second one, because 0,3,0 specificity beats 0,1,0 regardless of source order. This is usually what the author intends (supporting items keep their size), but reviewers should compute specificity explicitly rather than assume later = wins. Same check for phone padding overrides on `.tile` versus `.tile:nth-child(...)` padding. For text-fit tests on monospace fonts, value.length * fontPx * (0.6 - letterSpacingEm) <= column width minus padding is a cheap, deterministic proxy that avoids a headless browser in CI.
