Meta key mapping works in Chromium but not in Firefox (Arch Linux)
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
I am trying to do the following keyboard remaps:
map previousTab
map nextTab
on my Arch Linux laptop in Firefox. However, when pressing m-j or m-k, the page is only scrolled down and up respectively (the default behaviour for j and k, I assume the meta key is just getting ignored). However, when I tried Chromium with the same mapping, it behaves as expected.
To Reproduce
Steps to reproduce the behavior:
Try the following mapping in Firefox (and possibly in Chromium, to confirm that it works there):
map previousTab
map nextTab
Browser and Vimium version
Chromium: 97.0.4692.99 (Official Build) Arch Linux (64-bit)
Vimium (Chromium): 1.67
Firefox: 96.0.2
Vimium (Firefox): 1.67.1
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 and mappings in Firefox 96.0.2 and Chromium 97.0.4692.99, comparing the keyboard event behavior between browsers. Done means the Firefox mappings trigger previousTab and nextTab instead of scrolling, while Chromium behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100