Feature-request: restore default vimium keys on Options page
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Restore Default Key Mappings
Problem
Currently, when a user maps a certain key, and afterwards wants to restore it to the original key, he has to remember the key or look it up. When several keys were mapped, the easiest way is to re-install the extension altogether.
Suggested solution
To implement a "restore default vimium keys" on Options->Custom key mappings.
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 at the Options page's Custom key mappings interface and trace how user mappings are stored and displayed. Determine how the original Vimium mappings are defined, then add a restore-defaults action whose completion state is visible in that interface; verify that customized mappings return to their defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100