NumpadEnter location property seems incorrect
Open
Nobody has claimed this yet.
bug
Element Send Keys
Perform Actions
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
In chapter 17. Actions, section 17.4 Dispatching Actions:
\uE007 Enter 1
The spec indicates that key events dispatched for \uE007 "NumpadEnter" should have the location property set to 1. This key is located on the numpad though, so I would expect the location to be 3. This is consistent with a user pressing the real numpad Enter key on a US keyboard.
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 section 17.4, “Dispatching Actions,” at the linked WebDriver specification and inspect the NumpadEnter entry for U+E007. Confirm the intended key-event location value against the behavior of a physical numpad Enter key; done means the specification records the correct location consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100