Do not leak weak mods from tap dance to the interrupting keypress (#12471)
Tap dance callbacks may register weak mods; one case when it happens is when a tap dance registers a key with modifiers. When the tap dance is interrupted by pressing another key, these weak mods could affect the interrupting key (normally any stale weak mods are cleared at the start of action_exec() when handling a keypress event, but the tap dance interrupt check code is called later, and the weak mods left by that code were not cleared). Add another clear_weak_mods() call to preprocess_tap_dance() to make sure that the interrupting keypress is not affected by unrelated weak mods from the previous tap dance. Fixes #12445.
This commit is contained in:
parent
d3bf3d3b1c
commit
da6e888a32
|
@ -117,6 +117,10 @@ void preprocess_tap_dance(uint16_t keycode, keyrecord_t *record) {
|
||||||
action->state.interrupting_keycode = keycode;
|
action->state.interrupting_keycode = keycode;
|
||||||
process_tap_dance_action_on_dance_finished(action);
|
process_tap_dance_action_on_dance_finished(action);
|
||||||
reset_tap_dance(&action->state);
|
reset_tap_dance(&action->state);
|
||||||
|
|
||||||
|
// Tap dance actions can leave some weak mods active (e.g., if the tap dance is mapped to a keycode with
|
||||||
|
// modifiers), but these weak mods should not affect the keypress which interrupted the tap dance.
|
||||||
|
clear_weak_mods();
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue