Skip to content

fix(web): align the sidebar T3 Code lockup on a shared baseline - #1

Closed
meisolated wants to merge 1 commit into
mainfrom
fix/sidebar-brand-baseline
Closed

fix(web): align the sidebar T3 Code lockup on a shared baseline#1
meisolated wants to merge 1 commit into
mainfrom
fix/sidebar-brand-baseline

Conversation

@meisolated

Copy link
Copy Markdown

The wordmark and "Code" in the sidebar header were centered as two separate flex boxes, with a -translate-y-px nudge on the text to make them look level. Centering aligns boxes, not baselines, so the pair only lined up for a font whose ascent and descent match the default stack. With a custom interface font (Settings -> Appearance) the word drifts above the mark — measured ~2px on THICCCBOI (0.80em/0.20em vs Segoe UI's 1.079em/0.251em) — and the fixed 1px nudge does not scale with the interface font size either.

Now the mark and the word share one line box, so the mark rides the text baseline as an inline replaced element and follows whatever font is set. align-baseline overrides Tailwind preflight's svg { vertical-align: middle }. The fixed gap-1 becomes a real word space that scales with the font.

Before (interface font THICCCBOI, 16px): "Code" sits ~2px above the mark's baseline. After: not yet captured in a running client — happy to add the pair if wanted.

The wordmark and "Code" were centered as two separate boxes with a -translate-y-px nudge on the text. Centering aligns boxes, not baselines, so the pair only lined up for a font whose ascent and descent match the default stack: with a custom interface font (Settings -> Appearance) the word drifted ~2px above the mark, and a fixed 1px nudge does not scale with the interface font size either.

Put the mark and the word in one line box so the mark rides the text baseline as an inline replaced element, and replace the fixed gap with a real word space that scales with the font.
@meisolated

Copy link
Copy Markdown
Author

Reopened against upstream: pingdotgg#7312

@meisolated meisolated closed this Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant