Closed Bug 1862735 Opened 11 months ago Closed 11 months ago

Implement `action_sequence` for Synthesizing Mouse/Key Actions in WPT

Categories

(Testing :: web-platform-tests, enhancement)

Product:
Testing
Component:
web-platform-tests
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: dshin, Unassigned)

References

Details

See bug 1759031 comment 1.
Looks like WebKit doesn't support it either, but I see a fair bit of usage in WPT.
They're queued through Actions API defined here, which calls down to action_sequence, which errors out because our definition is empty.

Comparatively, Chromium has this defined.

Blocks: 1759031
Summary: Implement `action_sequence` for Synthesizing Mouse/Key Actions → Implement `action_sequence` for Synthesizing Mouse/Key Actions in WPT

(Moving to where webdriver component lives)

Component: web-platform-tests → Marionette
Product: Testing → Remote Protocol

This is not needed for Marionette but actually for web-platform-tests. So the original component was correct.

James, any reason why this is not defined for Firefox?

Component: Marionette → web-platform-tests
Flags: needinfo?(james)
Product: Remote Protocol → Testing

We do implement testdriver via marionette. We don't need anything in the testdriver-vendor file because we're using the default implementation in wptrunner (vs implementing it via vendor-specific, test-only, DOM APIs, as Chrome does in their internal infra).

Re: the original bug I don't know where that error message came from but I can't reproduce it locally.

Status: NEW → RESOLVED
Closed: 11 months ago
Flags: needinfo?(james)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.