Handle non-printable Vimium key mappings in insert mode
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
If I focus a textbox, it obviously makes sense for Vimium not to interpret A or whatever as a command. However, if I've mapped ctrl-g to a command, it seems reasonable for Vimium to continue to capture that keystroke, even within a textbox, rather than having Chrome's search bar come up.
Introducing an imap command seems like the most comprehensive solution, since that would allow a small number of mappings to be configured to work in text while the rest remain disabled. A "nimap"(normal-and-insert-map) would also be useful as it would avoid having to specify these commands twice.
This is prompted largely by the existence of auto-focusing textareas. Facebook Messenger in particular refocuses the textarea even after clicking off it into the chat.
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 tracing Vimium's existing insert-mode key handling and key-mapping commands to understand where text-input suppression is applied. Done means supporting configured non-printable mappings in text fields, with an imap command and optionally a combined nimap command, while leaving ordinary mappings disabled there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100