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
Hi, my application has a shortcut on the 'w' key on keyUp.
If I land on my application in a browser tab after using the default super+w to close another tab, the shortcut will fire without the user intending to.
So my question is, is there a way to avoid keyUp events that were started (keyDown) in another tab?
The text was updated successfully, but these errors were encountered:
The problem is, this could be painful to support if you have to do it for a lot of keys. It also still buggy. What if the user tabs away with super+w (registering the keyDown event) and then tabs back in the same way? You'd have the same problem.
You could maybe work around that by also watching for visibilitychange events. So something like:
Hi, my application has a shortcut on the 'w' key on
keyUp
.If I land on my application in a browser tab after using the default
super+w
to close another tab, the shortcut will fire without the user intending to.So my question is, is there a way to avoid
keyUp
events that were started (keyDown
) in another tab?The text was updated successfully, but these errors were encountered: