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

Different layouts problem #460

Open
notiv-nt opened this issue Jun 18, 2019 · 0 comments
Open

Different layouts problem #460

notiv-nt opened this issue Jun 18, 2019 · 0 comments

Comments

@notiv-nt
Copy link

Different layouts problem The MAIN problem with similar packages:

let's decide what is keyboard shortcuts?

Google > keyboard shortcuts > first link > :

In computing, a keyboard shortcut is a set of one or more keys that invoke a command in software or an operating system.

Keys? What is the keys?

Google > keyboard keys > images > :

image

So, what is the key here? maybe A? or F ? C? D? maybe.
If you want to press ctrl+a, what you should press?. Yes, right, the keys with ctrl and a inscriptions

But, what you should press here?

image

huh? Where is the letters? How can this be used at all? It has no labels

Maybe this?

image

Or this?

image

No, you will press this

image

Because it is on this place that the keys are located on the qwerty (as most popular layout)

image

Azerty, Qwertz, Dvorak, Colemak, Maltron, Jcuken and *enter you keyboard layout here*

Exampe: I have to press SHIFT + C to do something
On qwerty:

image

On dvorak:

image

Not so comfortable?

So here's the question: why?

  1. Why keyboard SHORTCUTS depends on user's layout? They are keyboard SHORTCUTS, not the actual letters that i must press? They are designed for ease of use
  2. Why do you use e.which if its deprecated? https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/which. (by the way keyCode is deprecated too https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/keyCode)
  3. Why dont you use e.code? Browser support? https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/code#Browser_compatibility ok, write a fallback for those who use IE or EDGE

https://codepen.io/notiv/pen/JQKxqX

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

No branches or pull requests

1 participant