-
Notifications
You must be signed in to change notification settings - Fork 90
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
keyboard shortcuts not working in an empty group #1149
Comments
There are specificies how Firefox Add-Ons work. These can't track shortcuts for non web pages - empty pages or pages representing Firefox chrome or web extension. You mentioned that loaded empty group and empty page. As page is empty - add-ons shortcuts does not work. Try to open any web page and use shortcut. If it works then it is your case and you can close this issue. |
Got it, didn't know that, thanks for your explanations. It's a bit of a shame when using "next/previous" shortcuts to cycle through groups, because landing in an "empty" group disrupts the keyboard navigation. Maybe this could be improved, and the plug-in could consider a group with just an empty tab as empty too ? |
Describe the bug
It seems when we are in an "empty" group (just showing an empty tab, if that's how your browser is set up), none of the shortcuts are effective anymore.
Whether it's the two that are configured by default, or any new custom one.
To Reproduce
Steps to reproduce the behavior:
Create at least 2 or 3 groups, open some websites in all but the last one (you may have to "load" the last group with an empty tab, though), then from a "populated" group, use shortcuts. Once you get to the "empty" group, you're stuck, you can't move away using shortcuts.
Expected behavior
Shortcuts should be usable too from an empty group, otherwise it just makes them useless overall.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
This might be related to issue #957
The text was updated successfully, but these errors were encountered: