Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267)

The Keyboard Map API has unfortunately been [rejected by Mozilla](https://github.com/mozilla/standards-positions/issues/300) and has not [received feedback from WebKit](https://bugs.webkit.org/show_bug.cgi?id=186680). My use case is essentially the same as photopea's, and it looks like using `keyCode` may be the only workable solution, if it works "consistently enough" for at least ASCII letters.

https://w3c.github.io/uievents/#determine-keydown-keyup-keyCode has what seems like a reasonable effort at specifying the behavior of this property. Are there more details available anywhere on the remaining differences across the major platforms (Windows, Mac, Linux) and browsers (Chrome, Safari, Firefox)?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/267#issuecomment-1238269841
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/uievents/issues/267/1238269841@github.com>