Key bindings become ineffective after a while on Github
See original GitHub issueI’m opening this issue because:
- [×] I’ll report a bug
- I’ll propose a new feature
Description
On github.com
Vim Vixen keybindings work initially after
opening a page but then become ineffective after a while.
For me this happens on the “notifications” page.
Sometimes the key bindings are ineffective from the start. E. g. I just opened this project: https://github.com/stratis-storage/stratisd and navigation vi j / h or C-u / C-d is not possible. Nor is closing the tab with d etc. This does not occur consistently; Vim Vixen worked when I opened the same URL in another tab.
The console does not print debug info in that state.
This behavior appeared only recently, presumably due to a change in Github’s JS.
Failure Information (for bugs)
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
- Open some project’s Github page.
- Try Vim Vixen key bindings; often they work for a while until they don’t.
- Optionally do stuff on other tabs and come back after a while.
- Vim Vixen key bindings have ceased to work.
System configuration
- Operating system:
Linux drift.m.i2n 5.18.16-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 3 15:44:49 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
- Firefox version:
firefox-103.0.1-2.fc36
- Vim-Vixen version: 1.2.3; last update: September 27, 2021
Console logs
Silence, unfortunately.
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:6
Top Results From Across the Web
Keybindings reset on invalid command · Issue #3295 - GitHub
Steps to reproduce the behavior: Open settings.json; Add keybindings for normal mode: ... Press Ctrl+u - nothing happens, because command doesn't ...
Read more >IDLE: refuse invalid key bindings #50988 - python/cpython
I tried to assign a new key(lctrl+lshift instead of lctrl+F5) for run- mode in option in v.2.5.2. I tried the new key and...
Read more >Leader key bindings which require a shifted key do not trigger ...
When a key binding which uses the leader key as its modifier (i.e. just LEADER ) and a shifted key is used, the...
Read more >Confusing keybinding error and behaviour #2147 - GitHub
warning that given keybinding will be effectively void because it is impossible to ever press a key which does not exist on current...
Read more >Unexpected keybinding config error · Issue #4992 - GitHub
This is happening any time I start terminal -- not a new tab in terminal, ... The quote may be found just after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m still encountering this, and actually, I’m now encountering this behavior consistently and immediately. I have disabled both the character keys setting, and also opted out of the command palette feature preview, and neither setting helped.
I have found that reloading the page fixes the vim vixen hotkeys temporarily though.
I opened a ticket open with GitHub, but seems they are stumped as I haven’t heard anything back in a while.
I have also noticed this, it seems non-deterministic and often randomly happens immediately for me too.
I’ve assumed this is not an issue with vim-vixen, but with GitHub doing something unwanted, but can’t really prove this either. I’ve followed GitHub’s own advice and turned off key bindings in my accessibility settings:
Currently, I’m noticing that no hotkeys work on one of my tabs: vim-vixen bindings aren’t working, and GitHub hotkeys like
?
andgg
don’t work. But I do feel like I’ve noticed vim-vixen stop working and the GitHub hotkeys take over (?
brings up the GitHub hotkey menu).In addition to this, I had github-refined installed as well, though disabling this didn’t seem to help either.
I can somewhat reliably reproduce this as well, if there is any way to help debug this.