Bind per-output app CSS for breadpad and breadman windows #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/per-monitor-app-css"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
theme::bind_windowusedbind_window_auto, which attaches only the per-output shared sheet. breadpad/breadman component rules resolve@bg/@accent/@blue/... from the display-global@define-colorblock, so on a monitor whose wallpaper differs those rules kept the session-global palette while shared-sheet widgets followed the output — a mixed palette on non-focused monitors (multi-monitor audit finding #2).theme::bind_windownow callsbind_window_auto_with_app_css, rebuildingbuild_css(with the userstyle.cssoverride) against the per-output palette; bread-theme inlines the named colours to hex for the bound tree.apply_livestays as the display-level / SIGHUP fallback.bread_theme::gtk::bind_window_autodirectly for its main and add-note windows (main.rs:376,619); both now route through the shared helper.clippy
-D warningsclean;cargo testgreen (all suites);cargo build --lockedunchanged.