Suggestion: Add Key Blacklist Support to useRecordHotkeys

[vedmakk]

Problem

Currently, useRecordHotkeys records all key presses while active. This creates an accessibility and usability issue:

When a user activates hotkey recording via keyboard (e.g., pressing a shortcut to change shortcuts), they are unable to use keys like Tab or Enter to navigate or interact with UI elements such as “Save” or “Cancel” buttons.

This behavior breaks the expected keyboard navigation flow and hinders accessibility—especially for users who rely heavily on keyboard input.

Proposed Solution

Add support for excluding specific keys from being recorded while useRecordHotkeys is active. This allows essential UI keys (like Tab or Enter) to remain functional for navigation and interaction.

Suggested API

Using a new options object as parameter:

const [keys, { start, stop, isRecording }] = useRecordHotkeys({
  useKey: false,
  blacklist: ['tab', 'enter'], // these keys won't be recorded
})

Alternatively, if you prefer to keep the current positional API style:

const [keys, { start, stop, isRecording }] = useRecordHotkeys(false, ['tab', 'enter']);

Why This Matters

• Improves accessibility for keyboard users
• Avoids UI deadlocks during keybinding changes
• Aligns with common UX patterns in customizable hotkey environments
• Simple, clean addition to existing API

Thank you for considering this improvement! I’d be happy to help test or contribute if this aligns with the project’s goals.

[JohannesKlauss]

I really like this feature, excellent idea. I think currently it makes sense to keep the positional API style for now. Would you be available to pick this up?

[vedmakk]

Great. Yeah, I'd like to implement it since I need it for a project anyways. I'll have a look and file a PR.

[vedmakk]

Hey @JohannesKlauss,
I’ve opened a PR here: #1268. Let me know if there’s anything you’d like me to adjust or if you have any feedback. Happy to help!