Fix the dangling --line-height-normal token in the reply preview #222
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-dangling-line-height-token"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
main's CI (
frontend-test) fails after the new-message composer merged: thenlddTokensguardrail (added in2a4fd4b, "Fail the build and the tests on asilently broken design token") flags a
var()without a fallback that resolvesto no defined property:
ReplyComposer.vue's.previewblock (the rendered reply markdown) still usedfont-size: var(--primitives-font-size-90); line-height: var(--line-height-normal).--line-height-normalis one of the Waggle type-scale tokens removed in theNLDD migration (#181), so it silently resolved to nothing. The composer branch
predated the guardrail, so it only surfaced once both landed on main.
Fix
Use the NLDD body font shorthand
--primitives-font-body-md-regular-snug- thesame token
base.csssets onbody(18px / snug 1.5) - which bundles size andline-height in one NLDD token.
.previewis body reading text, so it nowmatches the app's body typography instead of hand-setting size + a (broken)
line-height.
Guardrail test + the full frontend suite (651) pass; tsc and build clean.