Navigating to chrome-extension://{vimium's ID}/pages/ corrupts Vimium
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Go to chrome-extension://{vimium's ID}/pages/ via the url bar. The tab will immediately close and Vimium crashes and breaks. Going to the extension page shows Vimium as corrupted. Clicking repair fixes it.
Note, navigating to files in the pages/ directory, like vomnibar.html, works totally fine.
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
Reproduce the failure by navigating to chrome-extension://{Vimium's ID}/pages/, then compare it with opening a file such as vomnibar.html from the pages/ directory. Trace how the extension handles the pages/ path and verify that navigating there no longer closes the tab, corrupts Vimium, or requires repair.
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
- Mostly clear
- Newbie friendliness
- 35/100