If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

"Browser compatility" needs updating - Google Chrome now supports KeyboardEvent.key

RESOLVED FIXED

Status

Developer Documentation
API: Miscellaneous
P5
normal
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: Rob G, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

2 years ago
:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

The "Browser compatibility" reports that KeyboardEvent.key is not supported in Chrome. I tested the following demo in Google Chrome Version 47.0.2526.111 m, and it works.

http://jsbin.com/gibiqepebi/edit?console,output
Have you enabled any experimental flags? I got undefined in Chrome 47.0.2526.111.

But I read [1][2] that it might be shipped in Chrome 48 though.

[1] https://groups.google.com/a/chromium.org/d/msg/blink-dev/fn9qAu8z7JU/kZWEuqvJBAAJ
[2] https://www.chromestatus.com/feature/4748790720364544
(Reporter)

Comment 2

2 years ago
Oh, you're right, I did have the experimental flag set.
We could add a note that it works if the experimental flag set.

Rob G: want to do it?
(Reporter)

Comment 4

2 years ago
I would but I don't know what version it became available, and if there is support for "non-printable keys", "printable keys" and "dead key".
(Reporter)

Comment 5

2 years ago
Also, this is the flag that needs to be enabled: chrome://flags/#enable-experimental-web-platform-features
I've added a note (neutral on the version). Also, it will be worth investigating the support of "non-printable", "printable" and "dead" keys once it is activated by default.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.