Repository navigation
feat(browser): the owner's cursor gets there before the click - #93
Merged
Merged
Conversation
Click, type and select used to act first and tell the app afterwards, so the panel showed the page change before the bot's cursor moved. They now aim first: the element is found and scrolled into view, browser.action goes out with its point and, while someone watches, the click waits the cursor's glide (560 ms) before it happens. Nobody watching, no wait. The ripple in the panel starts as the cursor arrives.
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.
In the browser panel, the page changed before the bot's cursor moved and clicked. The daemon clicked first, waited for the page to settle, and only then sent
browser.action.Session::aim/aim_fieldfind the element and scroll it into view.click,type_textandchoosenow take thatAim.browser.actionwith the point first. While someone watches the browser (Browsers::watched), they wait 560 ms for the cursor's 520 ms glide, then act. With nobody watching there is no wait, so bots working unseen are not slowed.New real-Edge test
the_owner_sees_the_cursor_get_there_before_the_click: the click event arrives while the tool call is still running, and the tool answers at least 500 ms later. Onmainthis fails because the event comes after the click. fmt, clippy andcargo test --workspacepass; the daemon suite ran twice more with no failure.pnpm checkpasses (261).Still to see with the real Claude Code: open a bot's browser panel, ask it to fill a form, and watch the cursor reach each field before the field changes.