Arrow keys can't be excluded
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
I use the arrow keys to navigate between tabs. In GApps however, I'd need them to scroll up and down (j and k is used for switching between emails). Fortunately one can exclude specific keys only when managing vimium exceptions. However excluding special keys like does not work (I think the extension does not recognize to be special but rathers sees 5 indivual keys in that expression.
Is there a way to workarround this?
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 reproducing the Vimium exception behavior with , , , and while navigating tabs and GApps. Trace how the exception expression is parsed, then verify that arrow keys can be excluded individually without preventing their intended scrolling behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100