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

> No, that's not a given at all I'm afraid.

I think there is miscommunication. It is _explicitly_ stated that the key code is given as the **unicode code point** (or 0). See https://www.w3.org/TR/uievents/#determine-keypress-keyCode. When I wrote 

> in that surrogate pairs must be fully concatenated before emitting an event

I meant that this specific statement wasn't stated, but this statement _is_ a given since a broken surrogate pair is not a **unicode code point**.

> If things were appropriately defined in the spec then this spec issue would not exist :)

The reason this issue exists is not because the spec is not well-defined, but the fact there is misalignment between implementations and the spec. Again, there are two perspectives here:

 1. The browsers are being bad and implementing the spec wrong or
 2. the spec is too strict and we need to relax the conditions.

I'm stating that we should confess (1) and reenforce the current wording of the spec with specifics on surrogate point handling.

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

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