From e25351f51553389fa2d4dbc49bf68f6076636d9d Mon Sep 17 00:00:00 2001 From: stroblme Date: Sun, 23 Aug 2026 09:28:42 +0200 Subject: [PATCH] Correct the flow.css header: the canvas does pass colorMode MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The comment said the canvas follows the theme without a `colorMode` prop. It does not — React Flow stamps that prop on the wrapper as a class and defaults it to `light`, which collided with the app's own `.light` token scope and re-themed the whole canvas. The prop landed in 4e1898a; this is its reason. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016ZeGnqVsf5VHQqvz4HdUhN --- frontend/src/components/Flow/flow.css | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/frontend/src/components/Flow/flow.css b/frontend/src/components/Flow/flow.css index f313a6b..04e1a1a 100644 --- a/frontend/src/components/Flow/flow.css +++ b/frontend/src/components/Flow/flow.css @@ -2,8 +2,10 @@ * React Flow, routed through the design tokens. * * Scoped to `.react-flow` rather than added to index.css, so the canvas needs no - * tokens of its own and follows the theme in both modes without a `colorMode` - * prop. See the root DESIGN-GUIDELINES.md → Shells. + * tokens of its own. The `colorMode` prop is passed all the same: React Flow + * stamps it on the wrapper as a class, and `.light` / `.dark` are the app's own + * token scopes — an unset one defaults to `light` and re-themes the whole canvas + * inside a dark shell. See the root DESIGN-GUIDELINES.md → Shells. */ .react-flow {