Jean Chalard f2f9715319 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		2011-08-01 19:51:55 +09:00
..
res	Show settings and tab key accordingly	2011-07-31 20:00:00 -07:00
src/com/android/inputmethod	Try to compensate for a race condition.	2011-08-01 19:51:55 +09:00
Android.mk	Use InputMethodSettingsFragment	2011-07-09 11:25:54 +09:00
AndroidManifest.xml	Use InputMethodSettingsActivity	2011-07-11 10:15:03 +09:00
MODULE_LICENSE_APACHE2	Clarify licensing	2010-04-05 09:47:36 -07:00
NOTICE	Clarify licensing	2010-04-05 09:47:36 -07:00
proguard.flags	Removed unused import	2011-07-04 22:26:05 +09:00