KeyboardEvent.key (DOM Events Level 3) may simplify keyboard event handling
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
KeyboardEvent.key may simplify handling keyboard events. But since it is only supported in Gecko and Trident, a Polyfill would be necessary.
There is a (very old) polyfill that may be the base for a new implementation. A trivial subset mapping was implemented for some SmartTVs.
This would make map/keycode irrelevant.
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 reading src/map/keycode.js and compare its current role with the linked DOM Keyboard Event Level 3 polyfill and SmartTV subset mapping. Determine the required browser coverage and replacement scope before implementation. Done means a supported polyfill makes the existing keycode mapping unnecessary, with behavior verified across the targeted environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100