Skip to content

Fix custom chrome window drag regions - #65

Open
Febers wants to merge 1 commit into
dedene:mainfrom
Febers:fix/window-chrome-drag-regions
Open

Fix custom chrome window drag regions#65
Febers wants to merge 1 commit into
dedene:mainfrom
Febers:fix/window-chrome-drag-regions

Conversation

@Febers

@Febers Febers commented Aug 4, 2026

Copy link
Copy Markdown

Summary

  • Make the custom window chrome explicitly drag the window from empty header/background areas.
  • Allow non-interactive chrome text and review chips to start window drags.
  • Keep interactive chrome controls such as branch, PR, proxy icon, and split buttons out of the drag region.

Verification

  • Built GhosttyKit locally with ./scripts/build_ghosttykit.sh.
  • xcodebuild -project Zentty.xcodeproj -scheme Zentty -destination 'platform=macOS' -configuration Debug -derivedDataPath /private/tmp/zentty-derived CODE_SIGNING_ALLOWED=NO build passed.
  • xcodebuild -project Zentty.xcodeproj -scheme Zentty -destination 'platform=macOS' -configuration Debug -derivedDataPath /private/tmp/zentty-derived CODE_SIGNING_ALLOWED=NO -only-testing:ZenttyLogicTests/WindowChromeViewTests test passed: 60 tests, 0 failures.

Notes

A full xcodebuild ... test run completed compilation and integration tests, but had unrelated existing/environment failures outside this change area, including path-shortening expectations, programmatic resize layout assertions, a shortcuts preview key-recording assertion, and an OpenCode theme sync assertion. WindowChromeViewTests passed in the full run and in the focused rerun.

Make the custom window chrome explicitly drag the window from empty header space, non-interactive status labels, and review chips while keeping interactive controls out of the drag region. Add focused coverage for draggable and non-draggable chrome hit targets.

Co-authored-by: TRAE CLI <noreply@bytedance.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant