philc / philc/vimium

[Feature request] Allow configuration through Firefox policies

Open
#4,600 3 comments 4 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 can't define default options for the extension. The only apparent way to be able to copy configurations over to other machines is to download the backup JSON file from the extension's configuration page and then manually restore using that file.

uBlock supports configuration through policies, and I was wondering if I'm doing something wrong or if this isn't currently possible with Vimium. There's even a GitHub page by Mozilla using uBlock as an example.

I should note that I am using Home Manager, though it works just fine for uBlock and other policy configurations.

To Reproduce

  1. Try to define policy with contents of backed up vimium-options.json file, or even just a single option like scrollStepSize (either through Nix or normally).
  2. Vimium does not load the configuration.

See "3rdparty".Extensions; the other options are unimportant:

2025-01-02_01-30-14

2025-01-02_01-30-54

Browser and Vimium version

Firefox version 133.0.3 on Linux 6.12.7 #1-NixOS SMP PREEMPT_DYNAMIC Fri Dec 27 13:02:20 UTC 2024

Vimium version 2.1.2

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 locating Vimium’s Firefox-specific configuration loading and options initialization, then compare them with the Firefox policy shape linked in the issue. Done means a policy containing the backed-up options or a single option such as scrollStepSize is loaded by Vimium; add or run a focused regression check if the repository has one.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
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.