Vimium occasionally becomes disabled until configuration update
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Occasionally while using Chrome, Vimium will stop responding to any Vimum-specific keybindings across all tabs. As below, I don't have a clear sense of what is causing this, as it appears to happen randomly and intermittently throughout the day. Updating the configuration and saving appears to resolve the issue.
To Reproduce
I don't have a clear reproduction unfortunately, it appears to happen once every few hours where suddenly Vimum stops responding to my key presses, etc. I can resolve the bug by opening the extension's options and hitting "save changes".
Browser and Vimium version
Google Chrome: 131.0.6778.205 (Official Build) (arm64)
OS: macOS Version 15.1.1 (Build 24B91)
Vimium: 2.1.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by testing the reported intermittent loss of Vimium keybindings in Chrome 131.0.6778.205 on macOS 15.1.1, then compare the disabled state with the extension options flow. Use saving the configuration as the observable recovery condition; done means identifying and fixing the cause without requiring a configuration update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100