passNextKey does not automatically exit when used to enter Youtube fullscreen mode
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
passNextKey does not automatically exit when used to enter Youtube fullscreen mode. After entering the passNextKey mode and pressing F to enter fullscreen in a youtube video, the "Pass next key." prompt keeps showing on the bottom-right corner instead of disappearing and keystrokes keep on being passed just like in insert mode. No keys or key combinations can exit the passNextKey mode, including pressing ESC, or pressing the passNextKey hotkey again. (Not even exiting fullscreen mode and pressing ESC/passNextKey, only a refresh can clear the passNextKey state.)
To Reproduce
Steps to reproduce the behavior:
- Open any youtube video
- Press a key bound to passNextKey (I tried
<c-f>,<c-g>andg, all with the same issue. I'm using macOS so<c-f>shouldn't collide with any browser hotkeys.) - Press F to enter fullscreen.
- Observe that the "Pass next key." prompt keeps showing on the bottom-right corner, and any key press will still be passed on as raw inputs instead of being intercepted and interpreted as vimium commands.

Browser and Vimium version
Chrome: 112.0.5615.137
OS: macOS 10.15.7
Vimium: 1.67.4
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
No source file or test is named in the issue. Reproduce the passNextKey flow in a YouTube video, then trace how entering fullscreen affects the prompt and keyboard interception; done means fullscreen entry exits passNextKey mode and subsequent keys are handled as Vimium commands.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100