philc / philc/vimium

Feature request: remember hints for already followed links within the current tab

Open
#2,927 2 comments 0 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

I think this feature would speed up working with single page applications or other sites that dynamically add and remove links from the page.

For example:

  1. I'm at awesome-web-app.tld in view 0 and use vimium hints to click an element that doesn't navigate away from the single page application but goes to view 1. The hint for view 1 is a.
  2. I want to go to view 2 to check something, and use hints again. view 2 has some extra links in it. The hint is not relevant to this example.
  3. I have now checked it, and want to go back to view 1. The hint for view 1 is not a.

Step 3. with the feature: the hint is a.

I can try to implement the feature myself but I have never used CoffeeScript before and I don't know anything about the code base yet. Also, maybe not enable it automatically for everybody if it would be too heavy on CPU.

I'm using Vimium-FF on Firefox but I don't know how different it's from the code in this repository if at all.

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

No files or tests are named. Start by tracing Vimium's hint generation and current-tab state, then reproduce the three-view single-page-application flow described in the issue. Done means a revisited view receives its earlier hint without disrupting other views, with the CPU impact or opt-in behavior clarified.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.