fix: keep window draggable while Settings is open (#8) - #10
Merged
Merged
Conversation
The Settings scrim was `position: fixed; inset: 0`, covering the whole
window including the 36px title bar — which is the macOS window drag
region (`data-tauri-drag-region`). With the drag region covered, macOS
never received the mousedown that starts a window drag, so the window
couldn't be moved until Settings was closed.
Fix: start the scrim below the title bar (`inset: 36px 0 0 0`) so the
drag region stays uncovered and live. This also matches native macOS,
where the title bar stays at full opacity while a sheet is open.
Note: the 36px is coupled to `.titlebar { height: 36px }` in
routes/+page.svelte. The pending title-bar redesign will rework this
area; a shared `--titlebar-height` token would decouple it if this
outlives the redesign.
Reported by @unluckyquote. Fixes #8.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
msitarzewski
added a commit
that referenced
this pull request
May 31, 2026
The issue-8 fix (window draggable while Settings open, PR #10) is on main but landed after the v0.5.0 tag, so it's unreleased too -- it belongs in the same next-version notes. Adds a Bug fixes entry for it and credits @unluckyquote (Nik) alongside @bytepl in Acknowledgments. Retitled the file to cover both window fixes. Reported-by: Nik (@unluckyquote) Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
This was referenced May 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #8 — reported by @unluckyquote.
The bug
With Settings open, the dimming scrim (
position: fixed; inset: 0; z-index: 90) covered the entire window, including the 36px title bar that serves as the macOS window drag region (data-tauri-drag-region). With the drag region covered, macOS never received the mousedown it uses to begin a window drag — so the window couldn't be moved until Settings was closed.The fix
Start the scrim below the title bar (
inset: 36px 0 0 0) so the drag region stays uncovered and live. This also matches native macOS, where the title bar stays at full opacity while a sheet is open.Tested on macOS: with Settings open, the window drags by the title bar as expected, and click-outside-to-close still works.
npm run check: 0 errors.