Fix macOS top chrome drag rail / 修复 macOS 顶部窗口拖拽区域#3891
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Jun 10, 2026
Closed
esengine
approved these changes
Jun 11, 2026
esengine
left a comment
Owner
There was a problem hiding this comment.
Nice — a dedicated invisible drag rail scoped to .app--darwin .app-chrome--tabs is the clean way to restore a draggable target when the tab strip eats the chrome, and leaving the tab controls as no-drag keeps them clickable. Windows/Linux untouched. Thanks!
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
2 participants
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.
Summary
no-drag, while the rail exposes a subtle full-width hover indicator and accent-colored active state.Root Cause
Reasonix uses an inset/hidden macOS title bar, so the webview must explicitly provide draggable regions. The tab strip is interactive and opts out of Wails dragging, which can leave no reliable drag target when the top chrome is full of tabs.
Validation
pnpm --dir desktop/frontend run buildplatform=darwinverified that the rail is the hit target, the rail is draggable, tab controls remainno-drag, and hover/active indicators render at the same full width.Related: #3843, #3852, #3853