maiacore android keyboard app or something
f2f9715319
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 |
||
|---|---|---|
| dictionaries | ||
| java | ||
| native | ||
| tests | ||
| tools | ||
| Android.mk | ||
| CleanSpec.mk | ||