Re: [w3c/uievents] Review whether `key`, `code` etc should be present in legacy `keypress` events (Issue #349) from drwez on 2023-07-11 (public-webapps-github@w3.org from July 2023)

From: drwez <notifications@github.com>
Date: Tue, 11 Jul 2023 03:28:27 -0700
To: w3c/uievents <uievents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/uievents/issues/349/1630572606@github.com>

Thanks @garykac - unfortunately as has been discussed earlier, it doesn't make sense to leave the `key` attribute set to the value from the corresponding `keydown`/`keyup` in the case of non-BMP characters, _unless_ we assume that implementations only generate a single `keypress` per-`keydown` even for those - which has not historically been the case.

Whether it makes sense to set `key` in a `keypress` event therefore depends on the discussion in issue 346

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

Message ID: <w3c/uievents/issues/349/1630572606@github.com>

Received on Tuesday, 11 July 2023 10:28:33 UTC