Rename the command from "browser multi-click" to "browser batch-click"
per @AsenL's request. Updated across all files: implementation, action
enum, CLI wiring, router, output formatting, and all tests.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- multi_click_sequential_json: verifies 3 buttons clicked in order
with correct response shape (total, clicked, results array,
changed.url_changed + focus_changed, context, meta)
- multi_click_partial_failure_json: verifies MULTI_CLICK_PARTIAL
error with successful-prefix results and failed_at details when
second selector doesn't exist
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Increase DevTools URL discovery timeout from 15s to 30s for CI environments
- Relax snap_selector_flag_limits_subtree assertion to allow ±2 node tolerance
- Increase E2E test workflow timeout to 20 minutes
Chrome 146+ may enforce Trusted Types on certain pages, causing
innerHTML assignments to fail. Replace innerHTML with createElement
+ appendChild in install_select_fixture.
Three issues fixed:
1. Input.dispatchKeyEvent routes to Chrome's active tab, ignoring sessionId.
- type: add Target.activateTarget before key dispatch loop
- press: add Target.activateTarget before key dispatch
2. type command used minimal key definitions (just key+text) which didn't
trigger native text insertion on contenteditable elements.
- Reuse key_definition() from press module for full CDP key definitions
(code, windowsVirtualKeyCode, nativeVirtualKeyCode, unmodifiedText)
3. Contenteditable e2e test fixture had element at top:500px, whose center
(y=531) exceeded headless viewport height (513), causing click to miss.
- Changed to top:200px
Closes ACT-822
CDP DOM.focus fails on contenteditable divs (e.g., Lark/Notion/Slate editors)
with "Element is not focusable" (-32000). This change adds a JS .focus()
fallback and click-to-place-cursor for rich text editors.
Changes:
- Add TabContext::focus_element() with JS .focus() fallback when DOM.focus fails
- type command: detect contenteditable and click element center to establish
cursor position (required by Slate/ProseMirror internal cursor management)
- fill/focus commands: use focus_element() instead of raw DOM.focus
- Add E2E tests for type and focus on contenteditable elements
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
browser start --session sid: get-or-create semantics — reuses existing
session if found, creates with that ID if not. Works for both local and
cloud modes. Conflicts with --set-session-id (which always force-creates).
browser new-tab --tab tid: visible alias for --set-tab-id — creates tab
with custom ID, returns TAB_ID_CONFLICT on duplicate.
* [packages/cli]fix: send mouseMoved before mousePressed in dispatch_click (#220)
SPA frameworks (React Router, Vue Router, Next.js) require a prior
mouseMoved event to establish pointer hover state before the click
event synthesizes correctly. Without it, the router's click listener
never fires and the URL remains unchanged (url_changed: false).
Add a single mouseMoved dispatch at (x, y) with button=none before
the existing mousePressed/mouseReleased loop — matches Playwright's
standard click implementation.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [packages/cli]test: fix click_spa_navigation — use hash for pushState in about:blank (#220)
history.pushState with a path-only URL (/spa-destination) throws a
SecurityError in about:blank (null origin). Use a hash fragment
(#spa-destination) instead, which is always allowed.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
[packages/cli]test: add click_spa_navigation E2E test (#220)
Injects a SPA-style fixture (history.pushState on click with
preventDefault) into about:blank and verifies that browser click
triggers the router handler and returns url_changed=true.
Tests the mouseMoved fix — will fail until dispatch_click sends
mouseMoved before mousePressed in click.rs.
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>