Rolling key typing now working properly

[JinchunWei]

Hi,

I got my Keyclicks keyboard the other day. It's very nice.
However, after configured some tap and hold keys, I just noticed that keys are not working properly for me.

Configuration that I did: Rsft_T(KC_T), RCtl_T(KC_S). When I try rolling typing, instead of ts, it actually gives S. Doesn't matter how fast my rolling typing is, same result. So, not a tapping term issue.

Is there anything wrong with the configuration or it's something not behaving properly and need to be fixed?

PS: I have no change to the QMK settings. Permissive hold is disabled as well.

Please take a look. thank you!

[wolfwfr]

@JinchunWei

I just came across your post here and, even thought it's been a while, thought I'd share the following with you.

I came across this github issue thread for vial, where someone seems to confirm that this is expected behaviour for these quantum-keys.

QMK implemented a tap-dance feature called Hold on Other Key Press, that will execute the hold function of a key even if tapping term hasn't expired yet, IF another key is pressed while the tap-dance key is still engaged. This is similar but distinct from the permissive hold feature. Someone in this thread claims that this new feature is always applied to the quantum keys, and that is my experience as well.

I suspect this happens when you execute your rolling typing, where the keyboard still registers the right-shift as pressed, when the event for the other key comes in. Using quantum keys, the HOLD-function of the right-shift will then execute, even if the tapping term hasn't expired yet, yielding R_SHIFT + s => S