Commit graph

3 commits

Author SHA1 Message Date
CRT
ef3a5f6f7a host: a pane's own theme wins over a theme preview
A preview (the Theme Builder's, developer mode's, or one an automation left on through theme_preview)
replaced every site tab's theme, pane themes included, also on reload; "Theme for this pane" then
showed its choice checked while the page kept the preview. Reproduced live: a preview of Windows 98
turned a Paper pane into Windows 98 until the preview ended. Now a pane with its own theme keeps it;
every other tab shows the preview, as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 16:51:42 +07:00
CRT
52ab1fc00b host: AlertsConfig and ThemeConfig live in ungated modules, so the host compiles and tests without the tauri feature
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 16:05:27 +07:00
CRT
82382293a2 host: site themes are the host's (AppConfig::with_themes, commands::THEME)
theme_commands serves theme_get / theme_set / theme_preview / theme_scopes_get / theme_scopes_set
(shell-only, each checks its caller first; testkit::assert_theme_guards) over the theme state the
host now keeps: the owner's theme, account and pane themes, the Theme Builder preview. The app
only names its built-in themes and the two files (ThemeConfig). apply() themes every site tab
(script, cached Google font bytes, native background); page_scripts()/tab_background() serve a new
document; set_theme/set_scopes/set_preview are the app's own writers (backup import, dev mode).
A font install or removal re-themes the tabs in the host itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 14:10:43 +07:00