Skip to content

fix(ui): restore monospace font on the container name#116

Merged
nopoz merged 2 commits into
mainfrom
fix/container-name-mono-font
Jul 5, 2026
Merged

fix(ui): restore monospace font on the container name#116
nopoz merged 2 commits into
mainfrom
fix/container-name-mono-font

Conversation

@nopoz

@nopoz nopoz commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Problem

The container name in each row renders in the UI font (Rajdhani) instead of the monospace font it used before the #113 grid redesign.

Root cause

Pre-#113 the name was <v-chip> content, and cyberpunk.css sets font-family: "JetBrains Mono" on every chip (.v-application .v-chip). #113 rebuilt the name as a plain <span class="row-name">, which no longer matches that rule and falls back to the app default (Rajdhani).

Confirmed against a live pre-#113 build: the name there computes to "JetBrains Mono", monospace; on main it computes to Rajdhani.

Fix

Pin font-family: "JetBrains Mono", monospace on .row-name so the name matches the version tags and the pre-redesign look.

Verification

Built and loaded the container list: the name now computes to "JetBrains Mono", monospace, matching the adjacent version chips.

Pre-#113 the container name was chip content and inherited JetBrains Mono from
the global chip rule. The grid redesign made it a plain span, so it fell back to
the UI font (Rajdhani), changing the row's look. Pin JetBrains Mono on .row-name
so the name matches the version tags and the pre-redesign appearance.

JetBrains Mono runs larger than Rajdhani at the same size, so also hold the name
at the chip font-size (0.875rem) instead of the 1rem body default, keeping it in
line with the version tags. Verified live: the name computes to JetBrains Mono at
14px, matching the version chips.
@nopoz
nopoz force-pushed the fix/container-name-mono-font branch from fdd9313 to 69d36a3 Compare July 5, 2026 04:31
@nopoz
nopoz merged commit b015394 into main Jul 5, 2026
14 checks passed
@nopoz
nopoz deleted the fix/container-name-mono-font branch July 5, 2026 04:37
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