From 5c945c443b613764c819a5e5fa2c02358e191c89 Mon Sep 17 00:00:00 2001 From: Som Date: Sat, 22 Aug 2026 07:27:24 +0000 Subject: [PATCH 1/3] fix: increase markdown bold font-weight to 700 strong/b rendered at font-weight 500 in the new layout and with no weight override at all in the legacy layout, making bold text nearly indistinguishable from regular text. Closes #43597 --- packages/session-ui/src/components/markdown.css | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/packages/session-ui/src/components/markdown.css b/packages/session-ui/src/components/markdown.css index 1be5136680b7..c106792ccb84 100644 --- a/packages/session-ui/src/components/markdown.css +++ b/packages/session-ui/src/components/markdown.css @@ -73,7 +73,7 @@ strong, b { color: var(--v2-text-text-base); - font-weight: var(--font-weight-medium); + font-weight: 700; } /* Paragraphs */ @@ -346,6 +346,7 @@ body:not([data-new-layout]) [data-component="markdown"] { strong, b { color: var(--text-strong); + font-weight: 700; } li::marker { From 7e2bb079b8a64746ce21d79c4b83d63437d020e4 Mon Sep 17 00:00:00 2001 From: Som Date: Sat, 22 Aug 2026 07:27:31 +0000 Subject: [PATCH 2/3] fix: bound status popover height so long lists scroll MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Neither Tabs instance in status-popover-body.tsx had a height constraint, so tabs.css's existing overflow-y: auto never had anything to scroll within — the popover just grew off-screen with many MCP/plugin entries. Closes #43668 --- packages/app/src/components/status-popover-body.tsx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/app/src/components/status-popover-body.tsx b/packages/app/src/components/status-popover-body.tsx index 97982fa21f7b..4a7a4c4280dd 100644 --- a/packages/app/src/components/status-popover-body.tsx +++ b/packages/app/src/components/status-popover-body.tsx @@ -175,7 +175,7 @@ function ServerStatusPopoverView(props: { state: ServerStatusState }) {
}) {
Date: Sun, 23 Aug 2026 07:30:49 +0000 Subject: [PATCH 3/3] docs: note why bold weight is a literal 700 Addresses review feedback on PR #44097 asking whether a design-system bold-weight token should be used instead. Confirmed none exists (theme.css only defines --font-weight-regular/400 and --font-weight-medium/500), so the literal value stays; documented why so it isn't re-raised. --- packages/session-ui/src/components/markdown.css | 3 +++ 1 file changed, 3 insertions(+) diff --git a/packages/session-ui/src/components/markdown.css b/packages/session-ui/src/components/markdown.css index c106792ccb84..6f61331869d8 100644 --- a/packages/session-ui/src/components/markdown.css +++ b/packages/session-ui/src/components/markdown.css @@ -70,6 +70,8 @@ } /* Emphasis & Strong: Neutral strong color */ + /* Literal weight: theme.css defines no bold/semibold token today, only + --font-weight-regular (400) and --font-weight-medium (500). */ strong, b { color: var(--v2-text-text-base); @@ -343,6 +345,7 @@ body:not([data-new-layout]) [data-component="markdown"] { font-weight: var(--font-weight-medium); } + /* Literal weight: no bold/semibold token exists yet (see above). */ strong, b { color: var(--text-strong);