-
-
Notifications
You must be signed in to change notification settings - Fork 39.1k
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
SHIFT/CTRL + GRAVE_ESC not released correctly if SHIFT/CTRL is released first #1568
Comments
I have looked into how this issue is handled for layers. The function that is responsible for finding the right keycode to release is Since I suggest we store the generated keycode when |
This should be fixed. Closing. If it's not, reopen or open a new issue, please! |
To reproduce:
This will spam
`
until the next keypress.This is because when the ESC_GRAVE key is released, only the currently pressed mods are used to determine which keycode (GRAVE or ESC) gets released.
This looks like an issue that would arise with layers as well. We should look at how it's solved there.
The text was updated successfully, but these errors were encountered: