-
Notifications
You must be signed in to change notification settings - Fork 160
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
[BUG] - released key is still considered pressed #294
Comments
The workaround doesn't seem to work for scenarios in which one is trying to capture both 'command+z' and 'command+shift+z':
Log
|
Are you guys still having this problem? I was having an issue with nothing working after pressing spacebar and had to refocus the element to restore hotkey functionalities. I was using the package from npm. I then cloned this repo locally and built it to figure out the issue and realized that the version on github is newer than the one in npm and the issue I was having wasn't present in this one. Maybe this had already been fixed but wasn't published? |
I am experiencing the same bug as well. I was experimenting with my very first combinations command+z (undo), command+shit+z(redo) and it resulted exactly is what @mikhuang reported above. |
Describe the bug
When typing a capital letter using shift (shift+letter), sometimes it registers the keydown event for the upper case letter but then it registers the keyup event for the lower case letter. Since it doesn't have a keyup event for the upper case letter, it thinks that it's still presses
How are you using react hotkeys components? (HotKeys, GlobalHotKeys, IgnoreKeys etc)
It happens in all the use cases.
Expected behavior
It should detect that the key has been released.
Platform (please complete the following information):
It happens with Chrome, Firefox, Safari...
Are you willing and able to create a PR request to fix this issue?
No, because I found a workaround:
Include the smallest log that includes your issue:
What Configuration options are you using?
It happens with the default config.
The text was updated successfully, but these errors were encountered: