philc / philc/vimium

Feature request: Keep same letter combination for the same button/anchor text on following links via f

Open
#2,011 3 comments 3 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

As as vimium user, I always use links by pressing the f key and entering the relevant key combination.
As a web surfer, I browse sites that have consistent naming of a buttons and anchor tags.
Yet vimium applies different key combination for the same button values.

For example, github.com almost always has the button row: Watch, Unstar, and Fork.

Yet when I press f, "Fork" might get assigned SD or SF. So I can never trust a pageload to behave the same.

Or in pictures:

selection_141

selection_140

While this is nothing big of an issue for the github experience, I really got irked by it on the stackoverflow.com review queue, I can never be sure what combination to press to either Accept or Reject an edit. Sometimes skip is SS, then it is SD, then it is SE.

So as a feature request I kindly ask for vimium to be smart enough to keep to track the link key combination it has previously used for the same value of a button and anchor text to be able to just know the right shortcut for certain sites.h

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 link-hint flow activated by the f key and how it assigns combinations to buttons and anchor text. Define how the site and text are identified and persisted, then verify that repeated page loads give the same combination for matching labels while still handling conflicting or changing links.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.