Keyboard Hotkeys Don't Work Properly

Just wondering if anyone else has encountered this issue when doing reviews. About 50% of the time, the E/F hotkeys do not work unless you first hit ‘tab’ or click on the page using the mouse. Then, if you want to use the ‘backspace’ key (for the Double Check script) that won’t work unless you click on the page using the mouse. So this may be an issue with Double Check but I make a lot of stupid typos and don’t really want to disable the script. Having to constantly take hands off the keyboard and use the mouse slows me down a lot; the hotkeys are a game changer and it would be nice if this just worked. Has anyone else had this problem?

I haven’t had a problem with this.

I haven’t had any of these issues and I use double-check and the f-hotkey both regularly. Perhaps there’s something in your browser configurations that’s off?

Which browser are you using?

Lynx  

You too. I thought I was the only one.

2 Likes

Of course, without JavaScript, WK cannot be actually be used in Lynx. However… browsh to the rescue, support for pretty much anything a modern website/application can throw at you all in a text terminal, including animation and videos (albeit very blocky when rendered in a text terminal but full colour if the terminal supports true colour).

Loving this Lynx conversation, but I should also ask if OP is still having the issue lol. @bearymetric, has the issue resolved itself or are you still having problems?

-Nick at WK

Hello, no the issue has not been resolved. Also was not aware of Lynx but it looks cool. I’m using Firefox on Windows 10.

The primary issue just seems to be that only the main text box is “activated” during reviews, and to use ANY key except ‘enter’ you have to click on the page somewhere below the text box with the mouse.

The following scripts are also active:
-WK Open Framework
-Reorder Omega
-Review Audio Switch
-Utlimate Timeline
-Custom font
-Anime Sentences
-Double-check

Hey bearymetric! The first step is to turn off your scripts to see if the issue persists, and if it’s resolved it’s most likely one or more of the scripts. From there, you can try turning them on one by one to see which script(s) is the culprit.

-Nick at WK

I am also generally using Firefox (Windows at home, Linux at work) and am not seeing any issue with usage of hotkeys (I use them constantly) and have never seen any issues over several years. Of course, that does not help you, but does indicate that the root cause is likely something unique/specific to your environment. Next step is to figure out what that is. From your description it sounds like something is playing around with the window focus. It could be one of the WK user scripts (or some byproduct of a combination of 2 or more scripts) so I would recommend first investigating that angle. I do use two of the same scripts (WKOF, Utlimate Timeline) but do not use any of the others. Aside from WK specific scripts, it could also be some browser extension or add-on so that would be the next thing I would investigate. For example, I know that some password management extensions do some things to force input to what it thinks is a userID/password field. On occasion the add-on for the password manager I use identifies a field on a page incorrectly and tries to force input to that field.

1 Like