Re: [w3c/uievents] "keyCode" is the only way to work with KeyboardEvents now (#267)

@garykac Is this basic functionality going to be a victim of control creep?

User need: I want to be able to develop a web app with the shortcut Ctrl+K.

Institutional response: First, get the keyboard layout of the user. This is not yet supported by some of the browsers but we are applying political pressure so we expect them to eventually cave in. Then, deal with the fact that it returns a promise. That is because while we don't yet requre user consent, we maintain the option to do so in the future. Then, read your keyboard event's code and resolve it via the keyboard map. Ignore all browsers that didn't cave in and users who are cautious to give access to their keyboard layout.

Simple solution: Return the baseKey and let the developer handle Ctrl+K.

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

Message ID: <w3c/uievents/issues/267/1691346028@github.com>