Problems with autocomplete and german keyboard layouts
See original GitHub issueAlt + Any Keypress
invokes the autocomplete in GraphiQL.
On a german keyboard, the curly brace {
is typed by Alt + 8
.
That means that every time you type a curly brace in GraphiQL, the autocomplete will open.
The most annoying case is when autocomplete is invoked when typing something like query test {
, after which you would usually want a line break. When pressing enter, would select something from the autocomplete list.
I would suggest invoking autocomplete only on a more narrow combination, like Alt + Space
.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
T10252 Username autocompletion doesn't work with some non-US ...
The issue with ` is different: on German layouts, it acts as a combining character and does not generate a keypress event. The...
Read more >autocomplete unreachable via german keyboard - iterm2
The Shortcut CMD + ; is impossible without Shift on german keyboard. , and ; are on the same key und you need...
Read more >473932 - German Keyboard Layout (and maybe others) Defect
The German on-screen-keyboard displays everything as it should be, and input works fine. This bug is of course highly annoying, for the user...
Read more >Keyboard shortcuts do not work for german keyboard layout
So please give me some hint why the shortcuts are not working or fix the default keyboard shortcuts in the next release please....
Read more >Why is Apple autocomplete/-correct so bad…
I am unfortunately doomed to speak in different languages, I.e. German, French, Spanish, besides English. i have all 4 keyboards and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually, taking a closer look at the key maps, I think we should just check for the actual character typed in instead of using the
keyCode
, and resolve this issue easily. The primary intention for that code block is to limit the autocompletion firing for certain punctuators - such as ‘{’, ‘}’, ‘[’, ‘]’, and ‘)’. We should probably regex-match the keypresses intended to provide autocompletion for, or recognize the differences separately and prohibit them from firing autocompletion (mainly inspired by looking at some popular non-QWERTY keyboards).Let me PR this out.
Let me know if you have any other issues with this!