keyboard-map
keyboard-map copied to clipboard
WICG
API to get current keyboard mapping.
The current draft states the following non-goals: > * Identifying a keyboard layout or locale > * Being able to convert from a `code` value + modifiers into the `key`...
# The Question As of now, [the `getLayoutMap()` algorithm](https://wicg.github.io/keyboard-map/#h-keyboard-getlayoutmap) states: > If this's relevant global object's associated Document is not allowed to use the policy-controlled permission named "keyboard-map", reject the...
Fixes #44, related to #38. This PR clarifies "Privacy Mitigations" section to align it with the `getLayoutMap()` algorithm.
As I've noted in person a while ago, the Keyboard Map API as proposed exposes a high entropy fingerprinting surface. This is not acceptable from privacy perspective. As a result,...
While crawling [Keyboard Map](https://wicg.github.io/keyboard-map/), the following links to other specifications were detected as pointing to non-existing anchors, which should be fixed: * [ ] http://www.w3.org/TR/uievents-code/#code-quote This issue was detected and...
The privacy mitigations state: > As a first line of defense for the user, this specification requires that the API is only available from secure contexts and can only be...
I think it could be useful to be able to get the values for keys such as `AltLeft` and `Escape` etc. In general, macOS users expect shortcut hints to be...
Summary What problem would this solve? The problem this would solve is that on mobile there is no way to programmatically request the use of the soft keyboard which makes...
Allowing sites to selectively override some keys and not others is highly likely to create web compatibility hazards. Different browsers reserve different key combinations for their own use and inconsistent...
If the current keyboard layout is not ASCII-capable, the spec says that `KeyboardMap` should reflect the "highest-priority ASCII-capable layout". This is not a good solution for three reasons: 1. **You...
