philc / philc/vimium

Please add option to NOT activate Vimium until user explictly activate it (via browser-level extension key shortcut command)

Open
#4,234 3 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 developers, thank you for this good extension. I'm using it on Firefox.

There should be an option to NOT activate Vimium until user explictly activate it (e.g. via browser-level extension key shortcut command ('command' in manifest.json))

Reasons:

  1. To prevent interference with the web's original functions. Some web's functions rely on their own keydown event scripts.
  2. Still to prevent interference. Extensions like Vimium can't guarantee bugs-free (I just now opened another bug reporting issue 😂)
  3. Ease cpu when browsing. E.g. for some people like me, we don't use Vimium keys often, just on ~3% websites.
  4. To make recognizable browser fingerprints as few as possible

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 with manifest.json and the browser-level extension key shortcut command described in the issue, then trace how Vimium activation is currently entered. Done means Firefox leaves Vimium inactive by default and the requested browser shortcut explicitly activates it without interfering with normal page key handling.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.