Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are Shift or AltGr fallbacks sufficient? #126

Closed
r12a opened this issue Dec 16, 2016 · 1 comment
Closed

Are Shift or AltGr fallbacks sufficient? #126

r12a opened this issue Dec 16, 2016 · 1 comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@r12a
Copy link

r12a commented Dec 16, 2016

5.3.6. Guidelines for selecting key values
https://w3c.github.io/uievents/#keys-guidelines

If more than one key is being pressed and the key combination includes one or more modifier keys that result in the key no longer producing a printable character (e.g., Control + a), then the key value should be the printable key value that would have been produced if the key had been typed with the default keyboard layout with no modifier keys except for Shift and AltGr applied.

In some Hebrew keyboards the caps lock key also produces significant character assignments, like shift in most keyboards. Perhaps it is necessary to take that into account here ?

@r12a r12a added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Dec 16, 2016
@garykac
Copy link
Member

garykac commented Jan 31, 2017

This issue was moved to w3c/uievents-key#40

@garykac garykac closed this as completed Jan 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

No branches or pull requests

2 participants