- From: Andrey Korzinev <notifications@github.com>
- Date: Wed, 05 Jul 2023 08:36:52 -0700
- To: w3c/uievents-key <uievents-key@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents-key/issues/66@github.com>
The only keyboard is present in the spec now is Apple US English layout, but there is a whole bunch of different keyboards in Mac world that is tightly coupled with mac OS keycodes implementation. Just a few for a reference: US English (currently considered in spec as Apple-wide keyboard)  British English (note that `Backquote` keycap is located completely different from any other keyboard in spec)  Japanese (numeric row differs significantly from Japanese keyboard described in spec)  This differences already presented some implicit implementation details in Chromium and Firefox that behaves differently from what end-users see on their Apple keyboard keycaps and differs from Safari implementation (see https://bugs.chromium.org/p/chromium/issues/detail?id=1296783, https://bugzilla.mozilla.org/show_bug.cgi?id=1263302) Maybe we can revise a spec so it would clarify behaviour on mac OS browsers? Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents-key/issues/66 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents-key/issues/66@github.com>
Received on Wednesday, 5 July 2023 15:36:58 UTC