Pointer action subtype behaviour when subtype is unsupported
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
e.g., what happens when you send a touch action when the browser and/or device doesn't support it?
It's unclear whether Create a pointer input source is actually meant to be fallible (i.e., if the subtype is unsupported), nor and process pointer parameters merely checks if the subtype is one the spec defines.
Seemly the behaviour currently is Marionette/GeckoDriver gives "invalid argument" (https://searchfox.org/mozilla-central/rev/973000acec0cbf7211e0fad89ca00c352aeb8384/remote/marionette/action.js#132), WebKit does a bunch of aliasing (https://github.com/WebKit/WebKit/blob/f7fc51937f2ee3eb0258f99408985316f8b3e4d5/Source/WebKit/UIProcess/Automation/WebAutomationSession.cpp#L2254-L2263), and ChromeDriver I think supports everything everywhere.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the WebDriver sections on “Create a pointer input source” and “process pointer parameters” first, then compare the Marionette, WebKit, and ChromeDriver behavior linked in the issue. Determine whether unsupported pointer subtypes have defined behavior and document the intended normative outcome in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100