philc / philc/vimium

[Feature Request] Toggle scrollable areas

Open
#4,760 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
27k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

Hi,

I discovered the Vimium plugin today based on a suggestion given by a colleague. As a long time VI user this kind of navigation really suites me and I am currently in the process of discovering all the possibilities this tool offers. There are great concepts here and I really like the way it works! Although there are still some limitations on particular pages (like Atlassian) it works out quite well.

One thing that still is a little bit cumbersome is the way scrollable areas are selected. I know that I can press "f", look for the area I want and select it via the corresponding key binding, but there are cases where those keybinds are difficult to track down (sometimes overlapped, sometimes it is not clear which one to choose). What would be great is a key binding to toggle previous/next scrollable areas (like there is nextFrame for frames). That way with the nice hint on which area is currently selected, it would make it much easier to navigate through multi column pages.

Maybe something to consider for the next version.

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the existing f hint flow for selecting scrollable areas and review how nextFrame handles cycling through frames. Determine how the currently selected area is represented and how keyboard bindings are registered. Done means previous/next bindings can cycle through scrollable areas and the selected area remains visibly indicated.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.