`useHotkey` callback fire during active `useHotkeySequence` matching
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 719
- Forks
- 47
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
TanStack Hotkeys version
v0.9.1
Framework/Library version
next v16.1.6
Describe the bug and the steps to reproduce it
When a single-key hotkey (e.g. C) and a sequence starting with a different key but ending with that same key (e.g. G → C) are both registered, pressing the sequence fires both the sequence callback and the single-key hotkey callback.
To Reproduce
// Register a single-key hotkey
useHotkey("C", () => {
console.log("C hotkey fired");
});
// Register a sequence that ends with the same key
useHotkeySequence(["G", "C"], () => {
console.log("G → C sequence fired");
});
// now press G, then press C
// notice that both log fired
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
.
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
None
Terms & Code of Conduct
- I agree to follow this project's Code of Conduct
- I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
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 behavior with the useHotkey("C") and useHotkeySequence(["G", "C"]) registrations described in the issue. Trace how the two hooks handle the second keypress during an active sequence, then verify that pressing G followed by C fires only the sequence callback while standalone C still fires its hotkey callback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100