Consider retaining pointer properties between actions
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
It's currently unclear what happens in actions when pointer property values are omitted. I think the implied behaviour is that if a value (say pressure) is omitted, we use the default values from https://www.w3.org/TR/pointerevents/#pointerevent-interface (in this case 1).
That means that if you perform a pointerDown and specify pressure: 0.5 each subssequent pointermove action on that pointer also needs to specify pressure: 0.5 or the pressure will be implictly increased to 1.
A more sensible approach would be to apply the defaults for pointerdown, but then keep the values in the input state and only update then for pointermove actions which explicitly supply a value.
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
Start by reviewing the pointerDown and pointermove action semantics against the W3C Pointer Events specification linked in the issue. Define how omitted pointer properties should be initialized and retained, then update the WebDriver specification so the behavior is explicit and verifiable.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100