- From: Masayuki Nakano <notifications@github.com>
- Date: Thu, 01 Jun 2023 22:03:37 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 2 June 2023 05:03:41 UTC
And in the Firefox's case, the behavior is originated in the path to handle dead key of Windows. If you type a dead key and `KeyQ` (assuming it's invalid combination), then, a punctuation corresponding to the dead key and the character for `KeyQ` are sent with `WM_CHAR`s for the last `WM_KEYDOWN`. The non-BMP character key press works same as so (except the preceding dead key down/up sequence). Therefore, the behavior appears in historical reason. I don't know about Chrome, they might just emulate same behavior as IE and Firefox. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/346#issuecomment-1573148367 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/346/1573148367@github.com>
Received on Friday, 2 June 2023 05:03:41 UTC