diff options
| author |   Jean Chalard <jchalard@google.com> | 2011-08-01 19:06:54 +0900 |
|---|---|---|
| committer | Jean Chalard <jchalard@google.com> | 2011-08-01 19:51:55 +0900 |
| commit | f2f971531904026663a98629eec6eccf83e32faf (patch) | |
| tree | e5a3d3004dfeefa805a5010899cf69d972bf87a4 /java/src/com/android/inputmethod/deprecated/languageswitcher/InputLanguageSelection.java | |
| parent | e00d44d0c8a1420482121f2f3347def9ef430778 (diff) | |
| download | latinime-f2f971531904026663a98629eec6eccf83e32faf.tar.gz latinime-f2f971531904026663a98629eec6eccf83e32faf.tar.xz latinime-f2f971531904026663a98629eec6eccf83e32faf.zip | |
Try to compensate for a race condition.
This does not really fix the underlying bug, but it does fix
the apparent symptoms.
When the user presses space and a letter quick, the
onUpdateSelection handler may be called after the letter has been
actually committed. The keyboard then happily proceeds to clearing
the composition because it thinks space was pressed (or the user
moved the cursor, since it can't guess which happened).
This change removes this behavior when we are expecting an update
event from a keypress. This means the bug still exists if the user
presses space twice and a letter, and all events come after the
letter, but it is very very hard to reproduce this. There may be
other collateral damage when the user moves the cursor in the form
of race conditions, but likewise, they should be really hard to
reproduce.
Bug: 5100521
Change-Id: Ib05328c9b451bf6fe288ae00296fd283a9a4e863
Diffstat (limited to 'java/src/com/android/inputmethod/deprecated/languageswitcher/InputLanguageSelection.java')
0 files changed, 0 insertions, 0 deletions