feat(dioxus): implement W3C Actions API in the embedded driver

[goosewobbler]

Summary

Implements the W3C Actions endpoint (POST / DELETE /session/{id}/actions) in @wdio/dioxus-embedded-driver, which was previously wired to the not_implemented stub. Any WDIO command routed through the Actions API failed with unsupported operation ("not implemented for Dioxus embedded driver").

Closes #427.

Affected commands now unlocked

element.click(options) (.click({ button: 'right' }), .click({ x, y })), element.doubleClick(), element.moveTo(), drag-and-drop, and browser.action(...) / browser.actions(...) chains (pointer, key, wheel, pause). (Bare .click() already worked via the elementClick endpoint.)

Handler design

The Dioxus embedded driver has no native input path — unlike the Tauri driver (which dispatches real OS-level events through a native platform executor), every Dioxus command runs as JavaScript inside the webview through the bridge eval channel. So pointer/key/wheel actions are synthesized as DOM events dispatched on the element under the resolved coordinates, matching what a real browser produces for input:

• pointer pointerDown / pointerUp / pointerMove → MouseEvent (mousedown / mouseup / mousemove) dispatched on document.elementFromPoint(x, y). A primary press + release at the same spot synthesizes a click; a secondary (right) release synthesizes contextmenu — the events the browser would emit for real input, so element handlers fire.
• key keyDown / keyUp → KeyboardEvent on document.activeElement.
• wheel scroll → WheelEvent carrying deltaX / deltaY.
• pause → tokio::time::sleep.

Pointer position and pressed keys/buttons persist on the session's new ActionState so origin: "pointer" resolves relative to the last position and the DELETE release emits the matching keyUp / pointerUp events.

origin resolution (does NOT reproduce #423)

#427 is the Dioxus sibling of #423 (Tauri), where PointerMove was missing the origin field, so .click(options) silently clicked viewport (0, 0) and missed the element. origin is parsed and resolved correctly here from the start, mirroring the fixed Tauri handler:

• "viewport" (or no origin) → x/y are absolute viewport coordinates
• "pointer" → x/y are relative to the current pointer position
• element reference { "element-6066-…": "<id>" } → x/y are offsets from the element's in-view center, computed via getBoundingClientRect() (reusing the same rect lookup behind the element rect endpoint)

So element.click(options) — which WDIO sends as a pointerMove with an element origin and x/y defaulting to 0 — lands on the element's center, not viewport (0, 0). An unrecognised named origin is rejected with invalid argument rather than silently treated as viewport.

Verification

Run from packages/dioxus-embedded-driver:

Command	Result
cargo build	✅ Finished
cargo test	✅ 17 passed (8 new actions tests), 0 failed
cargo clippy --all-targets	✅ no warnings

origin resolution is covered by unit tests on the pure JS-builder + deserialization logic: the click-options shape (element origin, x/y = 0) deserializes to Origin::Element with the right element ref; the element-center JS adds half-width/half-height to the rect origin (the #423 regression guard); named "viewport"/"pointer" origins parse; and key/wheel/pause sequences round-trip. Cargo.lock is unchanged (no new dependencies — reuses serde, serde_json, tokio, uuid, axum, and the bridge).

Note on cargo fmt: this crate (and the whole repo) uses 2-space indentation per AGENTS.md, with no committed rustfmt.toml. Default cargo fmt --check reports diffs against every pre-existing file (it wants 4-space), so the new file matches the surrounding 2-space crate style rather than rustfmt defaults — running cargo fmt --write would reformat the entire crate.

Limitations

• Events are synthesized DOM events, not real OS input (this is the only mechanism the JS-only Dioxus driver has). Native browser default behaviors that only the engine triggers for trusted events (e.g. native text-selection drag, native context menu) won't fire; the dispatched events do drive application-level listeners.
• No deferred/stubbed action types — pointer (down/up/move/pause), key (down/up/pause), wheel (scroll/pause), and the null source (pause) are all handled. Pointer-move duration is honored as a pause before the final move (no intermediate-tick interpolation, matching the Tauri handler).

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR implements the W3C Actions API (POST/DELETE /session/{id}/actions) for the Dioxus embedded driver, synthesizing MouseEvent, KeyboardEvent, and WheelEvent via the JS bridge — unlocking element.click(options), element.doubleClick(), drag-and-drop, and browser.action(...) chains that previously returned unsupported operation. All four issues raised in the prior review round (buttons bitmask, tick-by-tick ordering, stale-element error type, button_to_mask overflow) are fully addressed in this revision.

• New actions.rs handler: tick-by-tick action dispatch across sources, correct buttons cumulative mask, origin resolution (viewport / pointer / element-center via getBoundingClientRect), and cross-call ActionState persistence for pointer position and held keys/buttons.
• ActionState in session.rs: minimal new struct carrying pointer position, pressed keys, and pressed buttons per action-source ID, initialised to defaults on session creation.
• Test stub fix in launcher.browser.integration.spec.ts: adds a fetch stub/unstub pair to prevent the new dev-server preflight probe from breaking unrelated handshake tests.

Confidence Score: 5/5

Safe to merge; all four blocking issues from the prior review round are fully addressed and the new handler behaves correctly for the primary use cases (.click(), .doubleClick(), right-click, drag-and-drop, key/wheel sequences).

The buttons bitmask, tick-by-tick ordering, stale-element error type, and button_to_mask overflow are all fixed. The two remaining observations (contextmenu on right-button drag, missing auxclick for middle-button click) are minor DOM-spec gaps that don't affect any WDIO test command described in the PR and were entirely absent from the previous not-implemented stub.

packages/dioxus-embedded-driver/src/server/handlers/actions.rs — the contextmenu position guard and auxclick synthesis are the two items worth addressing in a follow-up.

Important Files Changed

Filename	Overview
packages/dioxus-embedded-driver/src/server/handlers/actions.rs	New 877-line file implementing W3C Actions API via JS event synthesis; all four previously-flagged issues (buttons bitmask, tick ordering, stale-element error, button_to_mask overflow) are resolved, but contextmenu fires on any right-button release without a position guard, and auxclick is not synthesized for non-primary buttons.
packages/dioxus-embedded-driver/src/webdriver/session.rs	Adds ActionState struct (pointer_position, pressed_keys, pressed_buttons) and initialises it in Session::new(); clean, minimal change.
packages/dioxus-embedded-driver/src/server/router.rs	Wires the two new handlers (perform / release) to the /session/{id}/actions route, replacing the not_implemented stub.
packages/dioxus-embedded-driver/src/server/handlers/mod.rs	Exports the new actions module; single-line change, no issues.
packages/dioxus-service/test/integration/launcher.browser.integration.spec.ts	Adds a fetch stub in beforeEach and unstubAllGlobals in afterEach to prevent the dev-server preflight probe from breaking existing happy-path handshake tests; unrelated to the actions implementation.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant WDIO as WebdriverIO
    participant Router as Axum Router
    participant Handler as actions::perform
    participant Session as SessionManager
    participant Bridge as Bridge Eval Channel
    participant DOM as Webview DOM

    WDIO->>Router: "POST /session/{id}/actions"
    Router->>Handler: Json(ActionsRequest)
    Handler->>Session: read() — get timeouts + ActionState

    loop For each tick (0..max_actions)
        loop For each ActionSequence source
            alt Key source
                Handler->>Session: write() — update pressed_keys, recompute Modifiers
                Handler->>Bridge: eval(key_event_js)
                Bridge->>DOM: dispatchEvent(KeyboardEvent)
            else Pointer PointerDown
                Handler->>Session: write() — record pressed button
                Handler->>Bridge: eval(pointer_event_js mousedown)
                Bridge->>DOM: dispatchEvent(MouseEvent mousedown)
            else Pointer PointerMove
                Handler->>Bridge: eval(element_center_js) → [cx, cy]
                Handler->>Bridge: eval(pointer_event_js mousemove)
                Bridge->>DOM: dispatchEvent(MouseEvent mousemove)
            else Pointer PointerUp
                Handler->>Bridge: eval(pointer_event_js mouseup)
                Bridge->>DOM: dispatchEvent(MouseEvent mouseup)
                opt primary + same position
                    Handler->>Bridge: eval(pointer_event_js click)
                    Bridge->>DOM: dispatchEvent(MouseEvent click)
                end
                opt second click at same spot
                    Handler->>Bridge: eval(pointer_event_js dblclick)
                    Bridge->>DOM: dispatchEvent(MouseEvent dblclick)
                end
                opt right button
                    Handler->>Bridge: eval(pointer_event_js contextmenu)
                    Bridge->>DOM: dispatchEvent(MouseEvent contextmenu)
                end
            else Wheel scroll
                Handler->>Bridge: eval(wheel_event_js)
                Bridge->>DOM: dispatchEvent(WheelEvent)
            else Pause
                Handler->>Handler: tokio::time::sleep(duration)
            end
        end
    end

    Handler->>Session: write() — persist pointer_position
    Handler-->>WDIO: 200 OK

    WDIO->>Router: "DELETE /session/{id}/actions"
    Router->>Handler: actions::release
    Handler->>Session: write() — drain pressed_keys + pressed_buttons
    loop each held key (sorted)
        Handler->>Bridge: eval(key_event_js keyup)
        Bridge->>DOM: dispatchEvent(KeyboardEvent keyup)
    end
    loop each held button (sorted)
        Handler->>Bridge: eval(pointer_event_js mouseup)
        Bridge->>DOM: dispatchEvent(MouseEvent mouseup)
    end
    Handler-->>WDIO: 200 OK

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant WDIO as WebdriverIO
    participant Router as Axum Router
    participant Handler as actions::perform
    participant Session as SessionManager
    participant Bridge as Bridge Eval Channel
    participant DOM as Webview DOM

    WDIO->>Router: "POST /session/{id}/actions"
    Router->>Handler: Json(ActionsRequest)
    Handler->>Session: read() — get timeouts + ActionState

    loop For each tick (0..max_actions)
        loop For each ActionSequence source
            alt Key source
                Handler->>Session: write() — update pressed_keys, recompute Modifiers
                Handler->>Bridge: eval(key_event_js)
                Bridge->>DOM: dispatchEvent(KeyboardEvent)
            else Pointer PointerDown
                Handler->>Session: write() — record pressed button
                Handler->>Bridge: eval(pointer_event_js mousedown)
                Bridge->>DOM: dispatchEvent(MouseEvent mousedown)
            else Pointer PointerMove
                Handler->>Bridge: eval(element_center_js) → [cx, cy]
                Handler->>Bridge: eval(pointer_event_js mousemove)
                Bridge->>DOM: dispatchEvent(MouseEvent mousemove)
            else Pointer PointerUp
                Handler->>Bridge: eval(pointer_event_js mouseup)
                Bridge->>DOM: dispatchEvent(MouseEvent mouseup)
                opt primary + same position
                    Handler->>Bridge: eval(pointer_event_js click)
                    Bridge->>DOM: dispatchEvent(MouseEvent click)
                end
                opt second click at same spot
                    Handler->>Bridge: eval(pointer_event_js dblclick)
                    Bridge->>DOM: dispatchEvent(MouseEvent dblclick)
                end
                opt right button
                    Handler->>Bridge: eval(pointer_event_js contextmenu)
                    Bridge->>DOM: dispatchEvent(MouseEvent contextmenu)
                end
            else Wheel scroll
                Handler->>Bridge: eval(wheel_event_js)
                Bridge->>DOM: dispatchEvent(WheelEvent)
            else Pause
                Handler->>Handler: tokio::time::sleep(duration)
            end
        end
    end

    Handler->>Session: write() — persist pointer_position
    Handler-->>WDIO: 200 OK

    WDIO->>Router: "DELETE /session/{id}/actions"
    Router->>Handler: actions::release
    Handler->>Session: write() — drain pressed_keys + pressed_buttons
    loop each held key (sorted)
        Handler->>Bridge: eval(key_event_js keyup)
        Bridge->>DOM: dispatchEvent(KeyboardEvent keyup)
    end
    loop each held button (sorted)
        Handler->>Bridge: eval(pointer_event_js mouseup)
        Bridge->>DOM: dispatchEvent(MouseEvent mouseup)
    end
    Handler-->>WDIO: 200 OK

Loading

_{Reviews (11): Last reviewed commit: "fix(dioxus): deterministic multi-button ..." | Re-trigger Greptile}

[github-actions]

Standing release PR: #456 · 9 packages queued · open 158h 5m · ✅ ready to merge

Release Preview — 12 packages

Note: Labels on this PR are advisory in standing-pr mode. Bumps come from conventional commits in the standing PR; override by editing labels on the standing PR itself. Add release:immediate to bypass the standing PR and release this PR directly.

These changes will be added to the release PR (#456) when merged:

Changelog

@wdio/dioxus-bridge 1.0.0-next.3 → 1.1.0

Changed

• Update version to 1.1.0

@wdio/dioxus-service 1.0.0-next.3 → 1.1.0

Fixed

• stub dev-server probe in browser-mode launcher integration tests (fix(dioxus): stub dev-server probe in browser-mode launcher integration tests #493) (dioxus) Browser-mode test parity for Dioxus #472, Browser-mode error-handling polish (non-chrome browserName, unreachable dev server) #416

wdio-dioxus-driver 1.0.0-next.3 → 1.1.0

Changed

• Update version to 1.1.0

wdio-dioxus-embedded-driver 1.0.0-next.3 → 1.1.0

Added

• process Actions tick-by-tick across sources (Embedded drivers: process W3C Actions tick-by-tick across sources (Dioxus + Tauri) #491) (dioxus)
• accept pointerCancel in the embedded driver Actions API (dioxus)
• implement W3C Actions API in the embedded driver (dioxus) Dioxus embedded driver: implement W3C Actions API (/actions) — click(options)/drag/hover/key actions #427

Fixed

• deterministic multi-button release + pointerCancel click-chain reset (dioxus)
• set KeyboardEvent.code and deterministic keyup order (dioxus)
• guard button_to_mask against out-of-range button indices (dioxus)
• right-variant modifier keys + decreasing modifiers on release (dioxus)
• carry keyboard modifier flags on synthesized action events (dioxus)
• translate special-key codepoints and reset dblclick tracking on move (dioxus)
• synthesize dblclick for element.doubleClick() (dioxus)
• address review on the Actions handler (dioxus)

@wdio/tauri-service 1.2.0 → 1.3.0

Changed

• Update version to 1.3.0

@wdio/flutter-service 1.0.0-next.1 → 1.1.0

Changed

• Update version to 1.1.0

wdio_flutter N/A → 1.1.0

Changed

• Update version to 1.1.0

@wdio/electron-service 10.1.0 → 10.2.0

Changed

• Update version to 10.2.0

@wdio/native-core 1.0.0 → 1.1.0

Changed

• Update version to 1.1.0

@wdio/native-mobile-core 1.0.0 → 1.1.0

Changed

• Update version to 1.1.0

@wdio/native-spy 1.1.0 → 1.2.0

Changed

• Update version to 1.2.0

@wdio/native-utils 2.4.0 → 2.5.0

Changed

• Update version to 2.5.0

@wdio/react-native-service 1.0.0-next.0 → 1.1.0

Changed

• Update version to 1.1.0

After merge — predicted release

Approximate. The standing PR rebuilds against main at merge time; if other commits land first, the prediction may shift.

Package	Standing PR	This PR	After merge
@wdio/electron-service	10.2.0	10.2.0	10.2.0
@wdio/flutter-service	1.0.1	1.1.0	1.1.0 ⚠ escalated from 1.0.1
@wdio/native-core	1.1.0	1.1.0	1.1.0
@wdio/native-mobile-core	1.1.0	1.1.0	1.1.0
@wdio/native-spy	1.2.0	1.2.0	1.2.0
@wdio/native-utils	2.5.0	2.5.0	2.5.0
@wdio/react-native-service	1.1.0	1.1.0	1.1.0
@wdio/tauri-service	1.2.1	1.3.0	1.3.0 ⚠ escalated from 1.2.1
wdio_flutter	1.0.1	1.1.0	1.1.0 ⚠ escalated from 1.0.1

---

Updated automatically by ReleaseKit

[goosewobbler]

Greptile's two latest DOM-completeness observations — contextmenu not position-guarded against a right-button drag, and missing auxclick for non-primary clicks — are tracked as follow-up #494. Neither affects any WDIO command this PR unlocks (.click({ button }), .doubleClick(), moveTo, drag-drop), and both were absent from the prior not_implemented stub, so they're deferred rather than blocking. Added an in-code tracking ref at the synthesis site.