Re: [w3c/uievents] Bug in spec? event.key and casing (#169)

> If a modifier causes another letter, e.g., command key of Dvorak-QWERTY command keyboard layout, KeyboardEvent.key should represent the character coming from native key event.

Why? It seems like web developers need _portable_ behavior here. Not being able to figure out what a given key event refers to is a real problem. As a specific example, say you have an app that wants to bind Ctrl (or Cmd) + dollar sign to perform some currency-related action. You don't know the user's keymap, so you don't know whether a dollar sign involves shift or, if it does, which shift-less character it shares a key with. If you can't depend on `key` holding the appropriate printable character, I don't know of a reliable way to implement such a key binding.

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