Marc Durdin

> to me, conceptually, our anti-TWo caps handling and time-delay chording don't seem to be very compatible concepts for a generalized engine like Keyman. Can you explain further?

> So, about "time-delay chording": to me, a necessary pre-condition for time-delay chording like what you're intuitively expecting here is that we _don't_ use a greedy, first-come first-served approach. You're...

> As in... only add it to the multitap once the (second) tap is lifted (key-up), not on key-down? Well yes. A tap is a short (time) gesture, and the...

Moving this to 18.0 as it is a lower-priority issue.

Here's a repro with attached video. (Logging per #11277) Highlight in this video is at 0:11, where I intend to type a plain `r` but instead get `ȓ`. https://github.com/keymanapp/keyman/assets/4498365/d4c9db40-b2cc-4ac5-bb4b-cc53687572c1 ```json...

Another repro. Highlight is at 0:15 with `m` intended. (I didn't notice quickly enough to get history for the first unintended `r` with diacritic!) https://github.com/keymanapp/keyman/assets/4498365/a8851e3d-d6e9-47a9-8cf6-a57fcc405e44 ```json [ [ { "gestureSetId":...

> I'd ask if it was intended, but the rest of that gesture's lifetime indicates yes - you did go all the way to flick-end. I did no intentional flicks...

Added a note to the first video: > Highlight in this video is at 0:11, where I intend to type a plain `r` but instead get `ȓ`. And second: >...

> Is there additional setup I should take note of? Also, which browser was in use when this error occurred? I don't know in terms of additional setup; the issue...

I suggest we address this with Keyman Core refactor rather than trying to fix the existing core.