api.Document.keydown_event - Not Working To Spec On Android Chrome
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What information was incorrect, unhelpful, or incomplete?
The keydown event on Mobile Chrome is not implemented correctly, and thus shouldn't be marked as 'Full support' on developer.mozilla.org.
According to the bug report on bugs.chromium.org, this is a WontFix.
What did you expect to see?
As per spec, keydown should set key, which and code to match what key was pressed by the user. In Mobile Chrome, the properties for these are set to Unidentified, 229 and 0.
I think it would be helpful for developers uncovering this issue if there is an implementation note explaining this quirk on this page.
Did you test this? If so, how?
I uncovered this issue whilst trying to diagnose why keydown events weren't firing on a mobile web app.
MDN page report details
- Query:
api.Document.keydown_event - MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/Document/keydown_event
- Report started: 2021-10-20T10:14:48.255Z
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 browser-compat-data entry identified by the api.Document.keydown_event query and compare it with the linked MDN page. Record Android Chrome's Unidentified, 229, and 0 keydown values in an implementation note, then validate the compatibility-data entry against the repository's checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100