feat(e2e): add screen.doubleTapAt for viewport gestures

Merged
FG
6d ago
+147-21

What and why

Add screen.doubleTapAt(point, options?) alongside screen.tapAt. It sends a bare viewport double-tap through the existing performAt path on engines that declare the doubleTap pointer action. This lets test code edit a diagram label when a sibling SVG receives pointer input.

await screen.doubleTapAt({ x: 120, y: 240 }, { timeout: 1_000 });

The web-only browser.mouse.dblclick candidate is removed. The Playwright migration guide maps page.mouse.dblclick(x, y) to the shared API, and the changeset targets e2e.

Related to #1327 (runnable repro). Locator-relative double-tap and a coordinate double-tap tool for agent.act remain separate; this PR does not close the issue.

Separate test path fix

Use fileURLToPath in two hosted-session test helpers so temporary paths work in checkouts with non-ASCII characters or spaces.

Verified

Ran it locally: yes

The fixture regression failed before implementation because screen.doubleTapAt was missing. All 44 fixture tests now pass, including bare dispatch, timeout forwarding, validation, and step recording. The built CLI passes all 7 pointer tests in Chromium. The SVG regression verifies the trusted primary-button event sequence and confirms the label becomes Renamed.

e2e run tests/pointer.e2e.ts --video
āœ“ screen.doubleTapAt edits a label beneath a sibling SVG
Tests  7 passed (7)

The recording is local because GitHub CLI requires upstream write access to upload attachments.