- From: Masayuki Nakano <notifications@github.com>
- Date: Thu, 19 Oct 2017 01:04:41 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 19 October 2017 08:05:26 UTC
Oh, currently, Chrome uses "Process" for VK_PROCESS on Windows. The native virtual key code value means that the key event has already been handled (consumed) by IME. However, Chromium on Linux doesn't behave so. It fires ASCII character which is inputted when IME is closed even if I use Kana input mode. Edge fires keydown event with key value "Unidentified" but fires keyup event with key value with ASCII character which is inputted when IME is closed. I'm now planning to work on making Firefox dispatch keydown/keyup event even in composition. However, this key value inconsistency is now a big problem, which should refer or using better key value. @garykac what do you think? -- 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/75#issuecomment-337831089
Received on Thursday, 19 October 2017 08:05:26 UTC