You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From a team review of the Keyman for Android UX (#7161)
Holding backspace appears to desync context between web and app. After the first backspace, subsequent letters are not deleted from the textarea, but holding for a few seconds shows the keyboard going to upper case, suggesting web thinks it is at start of context. After that, even tapping the backspace key then does nothing, suggesting same thing.
Per @jahorton, does not appear to repro on iOS (15.0.268-stable).
Expected behavior
Backspace should work. Holding backspace should delete more rapidly.
I tried removing onLongPress from KMKeyboard and the problem went away. So it's a conflict between the Android gesture recognizer and the KeymanWeb code. Next question is: when did this arise -- and why? I may do a bisect to find out.
Describe the bug
From a team review of the Keyman for Android UX (#7161)
Holding backspace appears to desync context between web and app. After the first backspace, subsequent letters are not deleted from the textarea, but holding for a few seconds shows the keyboard going to upper case, suggesting web thinks it is at start of context. After that, even tapping the backspace key then does nothing, suggesting same thing.
Per @jahorton, does not appear to repro on iOS (15.0.268-stable).
Expected behavior
Backspace should work. Holding backspace should delete more rapidly.
Screenshots
Screen_Recording_20220831-060939_Keyman.mp4
Related issues
Keyman for Windows/macOS/Linux/iPhone/iPad/Android:
The text was updated successfully, but these errors were encountered: