Releases: github/hotkey
v2.0.0
What's Changed
- Fix querySelector by quoting templated value by @keithamus in #57
- Add tool to generate correct hotkey string for a given key combination by @theinterned in #59
- Update hotkey README to document hotkey string format by @theinterned in #62
- npm audit fixes by @theinterned in #63
- BREAKING: fixes
eventToHotkeyStringreturns doubled "modifier" when "key" is a modifier by @theinterned in #64 - BREAKING: Support comma as a hotkey by @colinwm in #71
- Update release.yml by @manuelpuyol in #72
New Contributors
- @theinterned made their first contribution in #59
- @colinwm made their first contribution in #71
- @manuelpuyol made their first contribution in #72
Full Changelog: v1.6.0...v2.0.0
Contributors
Assets 2
v1.6.1
What's Changed
- Fix querySelector by quoting templated value by @keithamus in #57
Full Changelog: v1.6.0...v1.6.1
Contributors
Assets 2
v1.6.0
v1.5.5
Before, the last registered element was always returned when multiple elements were registered with the same hotkey.
This PR changes this behavior for scoped hotkeys which were introduced in #49.
When the same hotkey is registered to multiple scoped elements, we can trigger the specific element that matches the criteria.
v.1.5.3
This release adds support for scoped hotkeys when the data-hotkey-scope attribute is specified.
v1.4.4
This fixes a regression in the eventToHotkeyString function in 1.4.3 which was caused by trying to normalise the event.key toUpperCase. The regression was because on macos the "Meta+Shift" plane is always lowercase, which is contrary to other operating systems. This is a regression because that was expected behavior as part of this package, and the fix in 1.4.3 broke this expectation while trying to fix another bug.
This change respects the event.key spacing, and elides the shift key only when the event.key matches case, returning Meta+Shift+p as a viable shortcut.
