issues
search
WICG
/
keyboard-map
API to get current keyboard mapping.
https://wicg.github.io/keyboard-map/
Other
31
stars
11
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Missing tasks in parallel steps in Keyboard Map
#46
dontcallmedom-bot
opened
3 weeks ago
0
Update Privacy Mitigations to align with getLayoutMap() algorithm
#45
bershanskiy
opened
11 months ago
0
Clarification needed regarding permissions policy integration
#44
bershanskiy
opened
11 months ago
0
Broken references in Keyboard Map
#43
dontcallmedom-bot
opened
1 year ago
0
Sync HTML output with bikeshed source
#42
dontcallmedom
closed
2 years ago
1
Use simpler phrasing for firing a layoutchange event
#41
dontcallmedom
closed
2 years ago
0
Add permission policy to privacy mitigation.
#39
snianu
closed
2 years ago
4
getLayoutMap() is unavailable in sub-context web applications due to privacy mitigations
#38
maymen1
opened
3 years ago
13
Support functional keys
#37
jespertheend
opened
3 years ago
0
Broadening the Scope of the Specification to Support Mobile Devices
#36
absurdprofit
opened
3 years ago
0
Don't allow capture of "system" keys
#35
martinthomson
closed
4 years ago
1
Don't allow configurable key overrides
#34
martinthomson
opened
4 years ago
1
Couple to fullscreen API
#33
martinthomson
closed
4 years ago
1
Non-ASCII layouts should be mapped according to the US keyboard
#32
tszynalski
opened
4 years ago
0
The map should always identify digit keys as 0-9, even if the layout requires Shift to type the digit
#31
tszynalski
opened
4 years ago
0
Keyboard Map introduces a high entropy fingerprinting surface
#30
rniwa
opened
5 years ago
7
Add explicit [Exposed]
#29
saschanaz
closed
5 years ago
0
Update Keyboard Lock Navigator Interface link
#28
bershanskiy
closed
3 years ago
1
Examples of Keyboard API uses
#27
bershanskiy
closed
3 years ago
3
Broaden the scope of the specification to support web IDEs
#26
spoenemann
opened
5 years ago
1
Duplicate definition of Keyboard interface
#25
foolip
closed
3 years ago
6
Incorrect status
#24
marcoscaceres
closed
5 years ago
1
Migrating to WebApps WG: Implementor interest?
#23
LJWatson
opened
5 years ago
0
Don't inherit EventTarget in partial interface Navigator
#22
foolip
closed
6 years ago
0
Add onlayoutchange
#21
phistuck
opened
6 years ago
0
Add `hasMulipleLayouts`
#20
phistuck
opened
6 years ago
0
Mobile device considerations seems too simplistic
#19
RByers
closed
6 years ago
0
Need definition for "ASCII capable" layout
#18
garykac
opened
6 years ago
5
"keyboardlayoutchange" event name is redundant
#17
domenic
closed
6 years ago
5
Should incognito mode be the same as normal?
#16
garykac
closed
6 years ago
2
navigator.keyboard.getKeyboardMap() -> navigator.keyboard.getMap()?
#15
domenic
closed
6 years ago
5
What object is keyboardchange fired on?
#14
domenic
closed
6 years ago
1
Are there grand plans for navigator.keyboard?
#13
domenic
closed
6 years ago
2
Consider a property instead of a get-function
#12
domenic
closed
6 years ago
1
Example is incorrect
#11
domenic
closed
6 years ago
0
Editorial: avoid InterfaceName.attributeName notation
#10
domenic
closed
6 years ago
2
Multiple keyboards?
#9
cynthia
closed
6 years ago
7
Privacy and fingerprinting concerns
#8
cynthia
closed
6 years ago
3
"keyboardchange" event trigger conditions could be more specific
#7
cynthia
closed
6 years ago
3
Name of "keyboardchange" event
#6
garykac
closed
6 years ago
10
Have getKeyboardMap return a Promise
#5
garykac
closed
6 years ago
1
TAG review
#4
garykac
closed
6 years ago
1
Request comments from Moz
#3
garykac
closed
6 years ago
4
Restricting to Writing System Keys
#2
garykac
closed
6 years ago
1
Do we need a way to return info about the "default layout"?
#1
garykac
closed
6 years ago
1