Troubleshooting Guide
General Best Practices:
- Don’t set two Keybindings to the same exact key combination (they may conflict and stop working).
- Exit out of the LingQ Tab when you’re not using it (i.e., end of day/study session) to prevent shortcuts from going out.
- Refresh the LingQ tab after long periods of inactivity.
Note: Below are just working lists that I came up with through trial and error. Still investigating when I can/have time!
Quick Reference Trouble Shooting When a Key Shortcut Isn’t Working:
Trouble Shooting Path 1:
- Check if the keybinding that isn’t working has the same key combinations as another keybinding.
- If one does, change one of the keybindings to a different key combination to prevent conflict.
- Refresh page and test new key binding.
Trouble Shooting Path 2:
- Reset Binds (wait until page refreshes)
- Toggle the extension off
- Refresh the page, Toggle the extension on again, and try the shortcut again (sometimes this works after that)
Trouble Shooting Path 3:
- Reset Binds (wait until page refreshes)
- Toggle the extension off
- Open the page (you want to use the keyboard shortcuts for) in a New Tab (make sure to close the tab that you were trying to get the shortcuts to work with—the tab/page may have been open too long).
- Toggle the extension on again.
- Refresh the New Tab from Step 3.
- Reset binds and rebind the shortcuts (with Rooster extension) to whatever you want it to be.
- Use/test the shortcut.
- Repeat steps 1-7 until the shortcuts work again if steps 1-7 don’t work the first time.
Note: It appears to be somewhat random (at least to me currently) when this 3rd method/troubleshooting path kicks in and works, so you may have to skip around and do any number of these combinations to get the shortcut to work—in the case I have detailed below. This is just what seems to be working for me. @roosterburton may come up with a fix/LingQ may figure their shortcuts out, but I just wanted to include this in case it helped anyone else!
P.S. Trying a different key combination for shortcuts that are finicky might help, too.
Part of Original Post (not troubleshooting guide):
Edit 5: See this reply for the next update.
Edit 4: See this reply for an update.
Edit 2: Note: I noticed the next page shortcut default for LingQ: [hold down] Shift + right arrow worked once I uninstalled the Rooster HotKeys extension, but when I reinstalled it, and tried to do the same default shortcut it stopped working.
Edit: Yeah, seems like the LingQ Keyboard shortcuts are flaky in general, so there’s not much to be done until LingQ figures this out, so I’ll uninstall for now and try to mess around with LingQ’s shortcuts and report them to their support team, and revisit this extension. (Looks great overall! Once it can work for me, I would love to reset a few—handful—bindings I would use. Note: If you don’t struggle with LingQ’s shortcut keys issues, this won’t apply to you.)
I’m not sure why it’s not working for me, but not even the original shortcut from the LingQs side works for me when it comes to moving to the next page. Are LingQs bindings (and maybe even these bindings) more friendly to non-mac users?
I tried setting the next page hotkey to the command (a.k.a. “meta” ?) + arrow right ( ), but it’s just doing the move to the next LingQ thing for me.
Additionally, in this case, the arrow right (by itself) also moves me to the next LingQ (which is what I want it to do anyway, but not on the command/“meta” + arrow right shortcut).
So it’s like it doesn’t even register that I’m pressing command/“meta” at all.
Edit: I can right/ left ( / ) arrow in either direction until it moves onto the next page—not very practical—though.
Anyone with a MacOS experience this? (either on LingQ—without the Rooster Extension—or with the Rooster extension)?
Also, the default keybinding for Translating (Shift + T) triggers my Firefox browser to open up a new tab, so it’s extra weird.
Any thoughts @roosterburton? (I understand this may be out of your scope here, just wondering.)