fix(window): restore maximized state and isolate titlebar controls from drag region - #209
pitangainnovare wants to merge 6 commits into
Conversation
b25c665 to
f62b1f3
Compare
|
Also fixes #183 as advertised. |
To clarify: PR #209 specifically addresses #183 (persisting and restoring window maximized state across sessions) and titlebar button event isolation on Linux. Issues #187 (scroll state restoration) and #189 (scrollbar clickability and arrow key scrolling) were actually resolved in |
|
Apologies! This makes perfect sense. I should have checked previous commits. Glad they're all fixed, though. |
Yes, both issues should now be marked as fixed in #189 was addressed by the scrollbar/resize-edge and keyboard-focus changes: #187 was implemented across the scroll-restoration series, starting with f0afaff and later hardened for asynchronous and paginated lists through a358002. These changes were authored by @lullabyX. I also tested the current branch locally on Ubuntu 26.04.1 LTS, running Linux 7.0 on x86_64, and both issues appear to be resolved. These issues were not fixed by PR #209 itself. Testing that branch simply included the newer changes already present in |
Summary
src-tauri/src/lib.rs):tauri_plugin_window_statewas initialized withoutStateFlags::MAXIMIZED, preventing the maximized state from being saved and restored across sessions. AddedStateFlags::MAXIMIZEDtowith_state_flags.src/components/TitleBar.tsx): Removeddata-tauri-drag-regionfrom the root titlebar wrapper to prevent WebKitGTK / GTK on Linux (especially Wayland) from capturing clicks on window buttons as window move drags. AddedstopPropagationon mouse down and click events for the minimize, maximize/restore, and close buttons.src/components/TitleBar.test.tsx): Added unit tests covering window control interactions and drag-region isolation.Closes #183