J/K scrolling polling rate issue?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Switching between J/K quickly causes scrolling to stop working until you let go of the keys.
When scrolling with J/K, if you hold J, let go of J and press K and vice versa, often times scrolling stops completely until you let go of both keys, wait perhaps ~400 milliseconds and press J or K again. In other words, the only way to consistently avoid this issue of switching between J/K quickly is to let go of J if you're pressing J and wait ~400 milliseconds then press K and vice versa--anything less and scrolling stops completely until you let go of the key.
Am I the only one with this problem?
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
Reproduce the reported failure by holding J, releasing it, and quickly pressing K, then repeat in reverse. No file, test, or entry point is identified in the issue; done would mean switching between J and K continues scrolling without requiring both keys to be released or a delay.
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
- Needs clarification
- Newbie friendliness
- 25/100