From c7291e05069e14b3f6617635c59302b524ba4ece Mon Sep 17 00:00:00 2001 From: Hugh Kaznowski Date: Sat, 5 Sep 2026 19:39:28 +0100 Subject: [PATCH] Delete ticket 025 file (already resolved by merged branch) Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01XFUNZwCvz3kcod3352ZR2o --- tickets/025-popout-tabs-dont-apply-theme.md | 11 ----------- 1 file changed, 11 deletions(-) delete mode 100644 tickets/025-popout-tabs-dont-apply-theme.md diff --git a/tickets/025-popout-tabs-dont-apply-theme.md b/tickets/025-popout-tabs-dont-apply-theme.md deleted file mode 100644 index 3c00715..0000000 --- a/tickets/025-popout-tabs-dont-apply-theme.md +++ /dev/null @@ -1,11 +0,0 @@ -# Popped-out tabs don't apply the active colour scheme/theme at all - -Reported: clicking "Open in new tab" (`PopOutButton`) opens a tab that doesn't match the current colour scheme/theme at all. - -Root cause: applying the colour scheme (`applyColorScheme`, `document.documentElement` class) and injecting any active custom theme's CSS is done entirely inside `useSettingsPanel()` (`webapp/src/lib/useSettingsPanel.ts`), and that hook is only ever called from `NavMenu.tsx:34`. Every popped-out standalone route (`StandalonePage` in `App.tsx`, used by `StandaloneLog`, `StandaloneParams`, `StandaloneRanged` for metrics/dashboards) wraps its children in `DocsNavProvider` only — it never renders `NavMenu` and never calls `useSettingsPanel()`. So a popped-out tab never sets the colour-scheme class or injects the custom theme `