Repository navigation
Test: Click the middle of the first page in split-click - #172
Merged
Merged
Conversation
A fixed click at x 700 lands in the second page on a runner's small window, which is already active, so the row was not driven there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Run 42602120049 reported split-click NOT_DRIVEN on the runner: "it did not move the active tab (active: page-b)". The scene posted its click at window x+700; on the runner the split panes sit at 276 and 660, so the click landed in the already active second page. The click now goes to the middle of the first page's region measured in the split capture.
🤖 Generated with Claude Code