- From: Masayuki Nakano <notifications@github.com>
- Date: Thu, 25 May 2023 18:08:09 -0700
- To: w3c/uievents-key <uievents-key@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 26 May 2023 01:08:14 UTC
Oh, sorry for the long delay to reply. When I was implementing `KeyboardEvent.key` in Gecko, I requested that there should be key values for Kana and Eisu keys of Mac. Then, probably I got a reply for that and I mapped them to `Kana` and `Eisu`. https://searchfox.org/mozilla-central/rev/ca52886e3b6051ca87861567e0c7628915f68780/widget/NativeKeyToDOMKeyName.h#552,577 > Windows ImeOn / ImeOff has been recently introduced, and AFAIK there is little Windows browser implementation for them currently. Yes, it is. They were introduced 2004 (Win 10 1903). Therefore, most users have already started using newer Windows than it. (FYI: Firefox still supports alter Windows too, though.) > If we apply this Mac Firefox mapping to Windows, we cannot distinguish VK_KANJI (*) and VK_IME_ON based only on KeyboardEvent.key, which is not straightforward. Right. On the other hand, some 3rd party IMEs seem to handle the IME specific keys before native applications. Therefore, their `.key` value may become `Process`. So, I'm not sure whether these keys are actually usable for web apps... -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents-key/issues/55#issuecomment-1563683710 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents-key/issues/55/1563683710@github.com>
Received on Friday, 26 May 2023 01:08:14 UTC