Keyboard input inconsistencies
Open
Nobody has claimed this yet.
Element Send Keys
Perform Actions
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
While implementing WebDriver keyboard input I found a handful of inconsistencies in the specification:
- https://w3c.github.io/webdriver/#dfn-normalised-key-value
- The codepoint
\uE006, currently mapped toReturnshould instead be mapped toEnter. The former is not mentioned (anymore) by the relevant UI Events spec.
- The codepoint
- https://w3c.github.io/webdriver/#dfn-code
- The keys
<and>each appear twice in the table. As the codes should represent a US keyboard the line"<"; ">"; "IntlBackslash"should be removed. OSLeftandOSRightare calledMetaLeftandMetaRightin the UI Events spec.- The key
\uE00Eshould map to thePageUpcode. (\uE01Fshouldn't) - The key
\uE00Fshould map to thePageDowncode. (\uE01Eshouldn't) NumpadAddis\uE025not\uE024NumpadSubtractis\uE027not\uuE026
- The keys
- https://w3c.github.io/webdriver/#element-send-keys
- "dispatch actions for a string" 4. Otherwise 2. requires "Dispatch a composition event with arguments "compositionstart" and undefined." but the UI Events spec mandates that the
dataattribute must be the empty string.
- "dispatch actions for a string" 4. Otherwise 2. requires "Dispatch a composition event with arguments "compositionstart" and undefined." but the UI Events spec mandates that the
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 comparing the referenced WebDriver sections for normalised key value, code, and element send keys with the linked UI Events requirements. Done means the duplicate entries, key mappings, names, and compositionstart data value match the cited specifications.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100