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

@hsivonen My description was in relation to the events received from the platform, not the way that those events are interpreted by the user agent, which I think we'd already discussed earlier as differing. :)

The `keypress` behaviour shown for IE and EdgeHTML don't really make sense, since the `charCode` field has a bogus value - since `keypress` is a legacy event having callers expected to use the `key` field to get at the real meaning, rather than simply using the standard `input` event, seems unhelpful.  That the two implementations differ in their choice of `charCode` value suggests that the behaviours were artefacts of an implementation choice, rather than a conscious decision.

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

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

Received on Thursday, 29 June 2023 09:03:37 UTC