- From: Gary Kacmarcik <notifications@github.com>
- Date: Fri, 07 Jul 2023 15:09:40 -0700
- To: w3c/uievents-key <uievents-key@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/uievents-key/issues/66/1626259767@github.com>
Enumerating all of the various Apple keyboards is beyond the scope of the spec, and the one example in the spec was meant to be representative (since it introduces keys that are specific to Apple keyboards). Note that we have a similar issue with laptop keyboards - there are many variations where manufacturers place standard keys in new locations. But we don't include them in the spec The only time is makes sense to include a new layout in the spec is when there is a new key that is introduced that doesn't exist on other keyboards. Simply having the standard keys in a different configuration is something we don't attempt to track. For example, the main part of the British English keyboard you give above is basically a standard 102-layout. The key with the \`~ label should have a `code` of `IntlBackslash` because of its position, even though the `key` attribute would be "`" or "~". Similarly for the Japanese keyboard where all the number keys are shifted. The `code` attribute will indicate the key's physical position (thus, the "1" key will have a `code` of `Backquote`, the "2" key will have a `code` of `Digit1`, ...). The one issue you mention relating to certain Apple keyboards mis-handling `Backquote` and `IntlBackslash` is a longstanding [issue](https://bugs.chromium.org/p/chromium/issues/detail?id=600607) with these keyboards that was thought to be fixed (perhaps only partially?). There was reason to suspect a hardware problem, and it's possible that Apple fixed the hardware issue so that the code fix in the browser is no longer needed. If it ends up that the bug cannot be fixed in the browsers, then we should consider adding a note (to the uievents-code spec) mentioning the issue. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents-key/issues/66#issuecomment-1626259767 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents-key/issues/66/1626259767@github.com>
Received on Friday, 7 July 2023 22:09:46 UTC