From 562026149f3b50a4f7536dcc379fa059006feee9 Mon Sep 17 00:00:00 2001 From: Lucas Berger Date: Wed, 10 Jun 2026 16:19:45 -0400 Subject: [PATCH] fix(06-06): remap primary-family container var so fallback all-day events stay solid MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The per-family remap (shared, member-1..4) only fills all-day pills whose Schedule-X colorName is registered. Member calendars absent from the current /api/me members list fall back to Schedule-X's built-in primary family, which was not remapped — so those all-day events degraded to the light tint. Remap --sx-color-primary-container as well so all-day pills stay solid in the fallback case too (production member-N calendars already covered). --- apps/pwa/src/styles/index.css | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/apps/pwa/src/styles/index.css b/apps/pwa/src/styles/index.css index 4f1da5b..28e1eed 100644 --- a/apps/pwa/src/styles/index.css +++ b/apps/pwa/src/styles/index.css @@ -103,6 +103,12 @@ body { */ .sx__date-grid, .sx__month-grid-day__events { + /* Fallback: Schedule-X uses the built-in `primary` family for any event whose + * calendar colorName is not registered (e.g. a member calendar absent from the + * current /api/me members list). Remapping it keeps all-day events solid-filled + * even in that fallback case, so the pill never degrades to the light tint. */ + --sx-color-primary-container: var(--sx-color-primary); + --sx-color-on-primary-container: #FFFFFF; --sx-color-shared-container: var(--sx-color-shared); --sx-color-on-shared-container: #FFFFFF; --sx-color-member-1-container: var(--sx-color-member-1);