Feature #1002
closed
- Status changed from New to Closed
After testing this out for a while, it doesn't improve anything to have it disabled, and I miss being able to move between fields with the arrow keys.
- Subject changed from Consider disabling keyboard navigation to Add a setting to control spacial navigation (moving between links and fields with the keyboard)
Some people really don't like it.
https://qoto.org/@josemanuel/110498328259593152
The best solution is probably to make it a configuration option.
The question now is, which should be the default state, enabled or disabled? On the one hand, people are not typically used to spatial navigation because it is not enabled by default on most browsers. So it might provide an initially unexpected experience, and the defaults should represent what the majority of users want. On the other hand, I think that the majority of users would prefer spatial navigation once they became used to it.
- Status changed from Closed to Feedback
- Description updated (diff)
- Status changed from Feedback to Closed
You mention this is regarding navigation when arrow keys. The forum thread that I've opened, is regarding vim based navigation.
If you aren't familiar with vim, it's a great tool to work with, even with a keyboard that doesn't have arrow keys (60% layout, 40% layout, etc).
Have you tried using Privacy Browser PC to see how well it works? That's probably the fastest way to answer your question.
I did try many browsers of vim based navigation, such as surf, vimb, etc. But none of them seem to have appropriate content blocking mechanisms & privacy controls.
I will try. But I need to compile it on my arch. Will take some time to test it soon. Tq for the PC build too.
Also available in: Atom
PDF