You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an React application has an action bound to the keydown event of a particular key and a handler for that action that causes the React application to re-render in such a way that there are temporarily no <HotKeys /> components mounted when the keyup event occurs, then the keyup event goes unregistered and react-hotkeys continues to act as if that the key is still held down.
This issue has been uncovered by #186: Now submatches are ignored by default, react-hotkeys thinking the first key is still held down prevents any future key combinations being correctly matched.
How are you using react hotkeys components? (HotKeys, GlobalHotKeys, IgnoreKeys etc)
Describe the bug
When an React application has an action bound to the
keydown
event of a particular key and a handler for that action that causes the React application to re-render in such a way that there are temporarily no<HotKeys />
components mounted when thekeyup
event occurs, then thekeyup
event goes unregistered andreact-hotkeys
continues to act as if that the key is still held down.This issue has been uncovered by #186: Now submatches are ignored by default,
react-hotkeys
thinking the first key is still held down prevents any future key combinations being correctly matched.How are you using react hotkeys components? (HotKeys, GlobalHotKeys, IgnoreKeys etc)
The text was updated successfully, but these errors were encountered: