Re: [w3c/uievents] Dead key symbols not included in KeyboardEvent (Issue #343)

On macOS, a dead key sequence is handled as IME composition on macOS. Similarly, if you see typed dead character as composition string in Linux, the IME which you installed into your system handles it as IME composition on Linux.

On the other hand, dead keys are treated as 2 sets of key events on Windows.

So if browsers expose the native input events to DOM events directly, the former works only when editable element has focus. In this case, browsers may send "Dead" key events as `keydown` with `Dead` key value.

The problem to explain which character is being typing with a dead key press is, the value is fixed at the end of the sequence (i.e., may be not related to the final result) and the value should be a combining character or not. Technically, dead key can be mapped with any character, and if OS provides different form character from standardized one, browsers need to convert them to get same result on all platforms. However, it's hard to maintain the conversion.

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

Message ID: <w3c/uievents/issues/343/1621055957@github.com>