Current Element Click Spec leads to Failed Assertion
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Problem:
For step 8.2.16 of Element Click, we dispatch pointer [move, down, up], which add [up] with "id" to the input cancel list.
Immediately after at 8.2.17, we Remove the input source with "id", which Assert none of items in the input cancel list has "id".
Proposal:
When dispatching tick actions, if subtype is "keyUp" or "pointerUp", we should remove any matching actions from the input cancel list.
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 with the Element Click steps 8.2.16–8.2.17, then read the dispatch tick actions and Remove the input source with "id" algorithms in the WebDriver specification. Trace how pointerUp and keyUp actions interact with the input cancel list. Done means matching actions are removed before the input source assertion, so the Element Click sequence no longer fails.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100