fix(web): raise the type scale so the portal is readable - #102
Conversation
The scale sat a step below browser defaults — xs 11px, sm 13px, base 15px — and text-xs carried most body copy in the OS (326 uses against 175 of text-sm, 124 of them 12px muted). The product read as small grey print. - Bottom of the scale is now the conventional 12/14/16, so 12px is reserved for genuine metadata rather than being the reading size. - Dark muted foreground lifted off the contrast floor. - Body copy in the primary OS views, and in the shared page header, empty state, and error state, moves up a step. Badges, table cells, and mono identifiers deliberately stay at 12px. Contrast was never the problem; scale was. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 50 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (14)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Task 13.
Contrast was never the problem — scale was. The muted foreground measures around 6:1 on card surfaces, which passes AA. What made the portal read as small grey print is that the type scale sat a full step below browser defaults and the smallest step carried most of the body copy.
Measured before the change:
--text-xs--text-sm--text-baseUsage across
components/,features/, andapp/: 326 uses oftext-xsagainst 175 oftext-smand 16 larger — and 124 of those weretext-xs text-muted-foregroundtogether. So the default reading size in the OS was 11px grey.Changes
0.69→0.74lightness). Modest, so secondary copy still reads as secondary.Test
components/typography.test.tspins the scale floor and asserts the muted lightness stays above the floor, so a future "tighten the design" pass can't silently walk it back down.Note
This is a system-level change — every screen shifts slightly. Worth eyeballing the board and Command at a narrow viewport before merging; those are the densest layouts and the most likely to reflow.
🤖 Generated with Claude Code