Bug 7422 - dead keys and backspace very unreliable on Android
Summary: dead keys and backspace very unreliable on Android
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.11.0
Assignee: Pierre Ossman
Depends on:
Blocks: keyboard
  Show dependency treegraph
Reported: 2019-10-31 12:24 CET by Pierre Ossman
Modified: 2019-11-06 09:40 CET (History)
0 users

See Also:
Acceptance Criteria:


Description Pierre Ossman cendio 2019-10-31 12:24:16 CET
Using any of the dead keys or backspace is very broken on Android, no matter the browser. The dead keys tends to get wedged in some way so every subsequent key gets modified. And backspace only works sometimes.
Comment 1 Pierre Ossman cendio 2019-11-04 11:18:06 CET
This only happens with the physical keyboard and only when the focus is on the canvas, not the textarea helper we use to open a virtual keyboard.

There seems to be some internal buffer at play here. The number of missing backspace events is the same as the number of character keys pressed before it. E.g. typing "abc" then three presses of backspace will go missing, but the forth works.

This seems to happen at a low level as attaching an event listener in capture mode to the document doesn't see any of those missing events either. So it smells like a browser bug.

This probably explains the weird dead key behaviour as well. The lack of a real buffer wedges the dead key state, so every key after that gets modified.
Comment 2 Pierre Ossman cendio 2019-11-04 12:33:35 CET
Reported to Firefox:


Tried to report it to Chrome, but their issue tracker is currently broken:


Not doing anything more right now.
Comment 3 Pierre Ossman cendio 2019-11-05 13:08:21 CET
As a workaround the user can press the control bar button to open the keyboard. This moves the focus to the input field instead of the canvas which works better.
Comment 4 Pierre Ossman cendio 2019-11-06 09:39:54 CET
It turns out that the chosen virtual keyboard also handles the physical keyboard. And this works just fine with GBoard. It's only SwiftKey that has an issue.

Unfortunately SwiftKey does not have a public issue tracker. I've sent them a report via their support form at least.

Closing this as we consider this a SwiftKey bug and we cannot track it.

Note You need to log in before you can comment on or make changes to this bug.