fix(meshcore): darken message scope/path/time metadata for readability (#3769)#3778
Conversation
#3769) The MeshCore channel-message metadata line — scope/region, relay path, and timestamp — rendered in --ctp-overlay0, which is too light/low-contrast to read comfortably against the message background. Step all three (.mc-message-time, .mc-message-route, .mc-message-scope) down to --ctp-overlay1, which is one shade darker/higher-contrast in every Catppuccin theme (darker than overlay0 on dark themes, and darker than overlay0 on the light Latte theme too). This satisfies the request that scope/path be at least as dark as the timestamp by darkening the whole metadata group together. CSS-only change; MeshCoreMessageStream tests pass (3/3). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VBLhGGNh35oMwTL53va1Y5
|
Claude finished @Yeraze's task —— View job PR Review
SummaryThis is a minimal, well-scoped CSS fix. The change is straightforward and correct. Here's my assessment across the requested dimensions: Code Quality & Best Practices ✅The change at /* Before */
.mc-message-time { color: var(--ctp-overlay0); }
.mc-message-route { color: var(--ctp-overlay0); ... }
.mc-message-scope { color: var(--ctp-overlay0); ... }
/* After */
.mc-message-time { color: var(--ctp-overlay1); }
.mc-message-route { color: var(--ctp-overlay1); ... }
.mc-message-scope { color: var(--ctp-overlay1); ... }The added comment at line 721–722 clearly documents the intent and references the issue number: /* Message metadata (time/route/scope) uses overlay1 — one step darker than
overlay0 for better readability in both light and dark themes (#3769). */Good: all three related classes are updated atomically so they remain visually consistent with each other. Potential Issues
|
Closes #3769
Problem
For MeshCore channel messages, the metadata line that shows the message scope/region and the relay path rendered too bright/light against the message background, making it hard to read. The timestamp on the same kind of line was easier to read.
Fix
All three metadata classes —
.mc-message-time,.mc-message-route(hop count + path), and.mc-message-scope— were usingvar(--ctp-overlay0). This bumps them one step down the Catppuccin gray scale tovar(--ctp-overlay1).overlay1is darker / higher-contrast thanoverlay0in every theme:overlay1is a darker gray thanoverlay0.overlay1(#8c8fa1) is darker thanoverlay0(#9ca0b0) against the light background.Per the issue, this darkens the whole metadata group together (time included), so scope/path are now at least as dark as — and in fact equal to — the timestamp, while everything reads more clearly.
Before / After
.mc-message-time--ctp-overlay0--ctp-overlay1.mc-message-route(path)--ctp-overlay0--ctp-overlay1.mc-message-scope--ctp-overlay0--ctp-overlay1Testing
CSS-only change.
MeshCoreMessageStreamtests pass (3/3). No new TypeScript errors introduced (the repo's pre-existingtsc --noEmitwarnings are unchanged).🤖 Generated with Claude Code