mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-22 17:22:47 +00:00
paseo-bot[bot]
9a3f3a0dc6
A recorded sequence like Ctrl+K Ctrl+J never fired. Pressing a modifier emits a keydown for the modifier key itself before the combo that holds it, so a chord waiting on its second step saw a bare `Control` first. That keydown matches no combo, and the resolver's fall-through reset the chord to step 0, leaving the following Ctrl+J to resolve as a first step and match nothing. A second step with no modifier was unaffected, which is why Ctrl+K J worked. A modifier keydown is the prefix of a combo, never a combo of its own, so the resolver now ignores it and leaves the chord where it is. The capture path already held that rule in `keyboardEventToComboString`; this exports the predicate behind it rather than adding a second notion of what a modifier key is. Closes #5265