Re: [w3c/uievents] Clarify `keypress` event handling for keys that map to non-BMP Unicode symbols (Issue #346) from jrandolf on 2023-06-02 (public-webapps-github@w3.org from June 2023)

From: jrandolf <notifications@github.com>
Date: Fri, 02 Jun 2023 07:21:53 -0700
To: w3c/uievents <uievents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/uievents/issues/346/1573821172@github.com>

@masayuki-nakano I think our browser logic is somewhat similar. It should be since Firefox and Chrome output the same sequence on Windows. On macOS, Chrome is just broken.

It seems we've come back full circle and came to the original solution I proposed. We should align with the OS behavior, i.e. one per OS event, this is table (1). For `keydown`, `keyup`, and `input`, let's stick strictly to the spec; only unicode code points, no broken surrogate pairs.



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

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

Received on Friday, 2 June 2023 14:21:58 UTC