VirtualKeyboard stops accepting keytouches after a few rapid keypresses

[DZiems]

Description

Typing keys in rapid succession on the virtual keyboard seems to disable/halt any further input. Pressing backspace quickly is a common use case affected by this.

Steps to Reproduce

1. Open a mobile instance of a mathfield and focus it to bring up the virtual keyboard.
2. Type any key or keys in rapid succession.
3. After about two or three rapid keytouches, input stops being received.

Actual Behavior

Keypresses stop inputing values.

Expected Behavior

Keypresses should continue to input values regardless of typing speed.

Environment

Is this a regression: did it use to work in a previous version?

(edit) I think so. On cortexjs.io/mathlive/demo, single keytouches can be executed in rapid succession (now this doesn't work), but multi-touches caused a focus bug (which was just recently addressed in issue #2244).

MathLive version
0.98.5 Using the following commit from this repo (most up-to-date version as of writing). [49f11e2]

Operating System macOS, Windows, iOS. Include the version iOS 17.1.2

Browser Safari and Chrome have this identical behavior.

[Abhishek-Nair-135]

I'm facing this issue as well. But was able to reproduce only on iOS devices.

[tomas-sipko]

Having the same issue, are there any updates?

[haypho]

I am also running into this issue. I pulled the repo and did some initial investigation. It seems like the the mathfield is getting blurred when typing into the virtual keyboard too quickly. I'm still doing more investigation, but thought I would post a comment here in case someone has some tribal knowledge that could assist quicker.

Here is the line that is blurring the mathfield: https://github.com/arnog/mathlive/blob/master/src/public/mathfield-element.ts#L1931

[haypho]

@arnog, any chance you can review #2567 for us? The following commands passed locally for me:

• npm run build
• npm run build production
• npm test
• npm run lint

[haypho]

Hey @arnog, I'm not sure if you get the PR notifications, so I am reposting here. I updated the PR with the recommended changes (thanks again!). I read through the documentation for contributors and I didn't see any clear next steps for myself. Are there next steps that I need to complete once #2567 is merged? For example, requesting a patch update to the library for NPM?

[haypho]

@arnog Thanks for merging this in for us! Is this going to be patched in the current version or are we going to have to wait for the year end release? Maybe the better question is when should we expect this to be published to npm?

[arnog]

This was fixed in 0.105.1