Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346)

Alright, so after some internal discussion with @drwez, we've designed the following solution:

 - Let's remark in the spec that `keypress` SHOULD be UTF-16. This will allow Safari's behavior and allow Firefox and Chromium to maintain current behavior.
 - `keydown`, `keyup`, and `input` shall remain the same.

@drwez @masayuki-nakano WDYT?

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

Message ID: <w3c/uievents/issues/346/1576652172@github.com>

Received on Monday, 5 June 2023 11:59:13 UTC