-
-
Notifications
You must be signed in to change notification settings - Fork 857
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
Add keyboard shortcuts #281
Comments
Whenever a site has built-in keyboard shortcuts, that adds the risk of interfering with default browser behavior (which can break accessibility), and also with browser extensions (for us Vimmers out there). Not saying it's a bad idea, just something to keep in mind and be careful of. |
Same, I use vim-like browser plugins, and if I'm lucky, any sites that use hotkeys will let me disable them. |
Of course. There should be an option to turn them off. |
And a way to show the current shortcuts (link + shortcut) |
I think both vim- and emacs-like keybinds would be great to have and they could probably even exist side-by-side. It'd be really cool if you could navigate the whole UI with keyboard only, that's something you can't even do with RES. It would also make the site more accessible for people who cannot easily use a mouse. Ideally the specific shortcuts would be fully configurable. |
What's even cooler, is navigating any site with a keyboard, which many of us currently do, using plugins like vim-vixen, trydactyl, etc. This is why I'm probably not going to add keyboard shortcuts to lemmy. This is a solved problem for the web in general, and any keyboard shortcuts would just conflict with that solution. |
I use Vimium myself too but I find site-specific shortcuts like RES' much more convenient and useful. Browsing typically works fine with external tools but interacting with the website (collapse replies, open post, up/downvote, reply, save etc.) is a lot better with "native" shortcuts rather than "pressing" the website's buttons with a long key combination. |
Some ideas:
The text was updated successfully, but these errors were encountered: