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

Azerty support #109

Open
vogloblinsky opened this issue Mar 3, 2016 · 2 comments
Open

Azerty support #109

vogloblinsky opened this issue Mar 3, 2016 · 2 comments

Comments

@vogloblinsky
Copy link

Is it in roadmap ?

@dmauro
Copy link
Owner

dmauro commented Mar 4, 2016

No. I'm not very focused on this right now because I've been pretty happy about where it's at. But if someone wants to write support to offer custom keyboard mappings, I'd love to review and merge it in :)

@jlowcs
Copy link

jlowcs commented Jul 8, 2016

Just an idea, but even though there is still no support for event.key on Safari (although hopefully coming soon), we might be able to use that instead of event.keyCode to detect some keys. For instance, the -/6 azerty key generates an event with the same keyCode (which is the same as the 6/^ qwerty key), but a different key property, depending on whether shift was pressed. In other words, do not use the code of the key (which might match a different character depending on the keyboard layout), but the character itself.

It should still work the old way when event.key is not supported though, for older browsers (and Safari).

https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/key

https://bugs.webkit.org/show_bug.cgi?id=69029

If that sounds like a good idea to you @dmauro, I might try to implement it soon.

Edit: FYI, I kinda need that feature, as I wish to be able to use - as a shortcut in my app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants