-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix minimal UI terminal top-row hit testing #6073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+300
−39
Merged
Changes from 3 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
2685f38
test: cover minimal terminal titlebar hit testing
austinywang eaa049e
fix: keep minimal terminal top row clickable
austinywang 45049b3
Merge remote-tracking branch 'origin/main' into issue-6066-minimal-ui…
austinywang 4a0cbc1
test: move titlebar hit test out of large suite
austinywang 31df166
fix: preserve titlebar control hit testing
austinywang b6198ed
test: guard titlebar band preconditions
austinywang 7a74b84
test: use Swift Testing for titlebar hit tests
austinywang 293b605
fix: defer titlebar double-clicks over terminal
austinywang cedb2fa
perf: reuse terminal hit in titlebar routing
austinywang 44e1711
chore: normalize project file
austinywang 2fa0b9f
fix: defer app titlebar double-clicks over terminal
austinywang 227c6dc
fix: bound terminal titlebar hit lookup
austinywang 2b98ced
fix: align chrome titlebar terminal routing
austinywang 891801b
Merge origin/main into issue-6066-minimal-ui-toolbar-hittest
austinywang 0288a7f
perf: lazily resolve terminal titlebar hits
austinywang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
XCTAssertGreaterThanOrEqualrecords a failure but does not stop execution. If the window geometry unexpectedly placespointInWindow.ybelowtitlebarInteractionBandMinY, the guard assertion fires butassertHitFallsInsideHostedTerminalis still evaluated. Because the hosted terminal fills the entirehost.bounds, a click anywhere on it would route to the terminal even without the fix — so the second assertion would likely pass on the old code as well, making the regression test give a false sense of coverage while only the guard shows as failing. Adding areturn(or usingXCTSkipIf) after the guard assertion ensures the test aborts rather than silently exercising the wrong scenario.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in b6198ed by converting the titlebar-band preconditions to guard/return checks in the new focused test file, so the assertions cannot continue on the wrong geometry.
— Claude Code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Superseded in the current test file: the titlebar-band geometry check now uses Swift Testing , so the test exits before evaluating the hit assertion if the point is outside the fixed band.
— Claude Code