-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Move Pointer to Next/Previous Link #312
Comments
What would be the "order" of links on the page? The height and optionally the width? The order of the characters you need to press? Order inside the DOM? Something else entirely? I personally can't decide between them, as for me it doesn't feel like there is a proper order of links on a page, but I do see the value in having something like this, just unsure how... |
With text-based browsers it is usually the order inside the DOM. I would say it is similar to in mainstream browsers when you focus an element and press The one benefit I see for using position on the page is that then you can have the notion of going "up/down/left/right" rather than "forward/backward" in the link list. But to take advantage of that you would need 4 more actions. I would prefer using the DOM, since it is more familiar, but if you find a way to intuitively make the spatial movement, I wouldn't mind that. Qutebrowser has this implemented as a setting. It would be nice if you could implement both ways of navigating links and leave it up to the user which one they want as well. |
Checklist
:help
documentation using/
for helpful informationAddition or change
In a lot of text-based browsers there are shortcuts for moving the cursor to the next link on the page. For example, see the last few shortcuts under "Page/Cursor motion" here for W3M. It would be nice if Vieb also had an action to move the pointer to the next/previous link.
Alternatives considered
You can open hints from pointer mode, but I want a way to cycle through adjacent links on a page.
The text was updated successfully, but these errors were encountered: