First of all, the information in this example should be represented as something more algorithmic so that it is less subjective. And "printable char" is not a good term to use.
We need to:
(1) confirm current behavior in FF/Chrome on Linux/Win/Mac with French and Dvorak keyboards. Identify any inconsistencies.
(2) verify there are no technical issues that make it difficult to have Dvorak ctrl-5 producing |key| = '5' (instead of 'q', which is the non-Dvorak value for that key).
From @garykac on November 3, 2016 21:28
First of all, the information in this example should be represented as something more algorithmic so that it is less subjective. And "printable char" is not a good term to use.
See discussion in the Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=527111 Specifically about the inconsistency between bullet pt 2 and 3 in example 33.
We need to: (1) confirm current behavior in FF/Chrome on Linux/Win/Mac with French and Dvorak keyboards. Identify any inconsistencies. (2) verify there are no technical issues that make it difficult to have Dvorak ctrl-5 producing |key| = '5' (instead of 'q', which is the non-Dvorak value for that key).
Copied from original issue: w3c/uievents#113