Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267) from Gary Kacmarcik on 2020-07-01 (public-webapps-github@w3.org from July 2020)

From: Gary Kacmarcik <notifications@github.com>
Date: Wed, 01 Jul 2020 15:45:19 -0700
To: w3c/uievents <uievents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/uievents/issues/267/652682053@github.com>

To identify the key that produces the 't' character, you can use the [Keyboard Map API](https://wicg.github.io/keyboard-map/). This will tell you which `code` is associated with each character.

Because of how inconsistent the currently implementations of `keyCode` are, it is not practical to specify the current behavior.

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

Received on Wednesday, 1 July 2020 22:45:31 UTC