Bug: 8911672
Change-Id: I5d5635949530a67f95e5208986907251b7bce903

This constant is better located in SuggestedWords.
Or it could be in Constants, that would be fine too.

Bug: 8636060
Change-Id: I3e721bb1e2559f028dce8929eceadfe0478c5924

Followup to IL66

Change-Id: I067e72c36f483cc3e3b24736c01843531298b507

Bug: 8636060
Change-Id: Iec56bce362ebfc52fedab02b127978abb4f3c7f9

Bug: 8636060
Change-Id: I624a45500603dfad355ee3b8b794b2d895219c0b

Bug: 8636060
Change-Id: Ib13a54854e30afb79217a0a1f2aeca50a95ba155

Bug: 8636060
Change-Id: I3b144993e2bcd552f9b292b8f057c9db4216125c

Bug: 8636060
Change-Id: Ic051e5d5514d270101b0571a2d30e2caa8f85bc1

This also fixes the coordinates passed to logOnDelete and
log onSeparator.

Bug: 8636060
Change-Id: I4703d61ad7de76b501adca18df3a69e06450c9a1

This is fine because getKey{X,Y} is idempotent for any
non-keyboard coordinate value.

However this makes a net change : the x,y values passed to
LatinImeLoggerUtils.onNonSeparator are now different.
The point is however that they used to be wrong. The logged
values used not to account for the keyboard padding that
is present on tablets, and in the simulating tools we don't
know about that padding so we couldn't use the coordinates.
The catch here is that other calls like LoggerUtils.onSeparator
should follow suit, but this is too big a change to do it at once.
Follow-up changes will fix them too.

Bug: 8636060
Change-Id: If4b3d3cb1ed4b44c35f23e66aba3b5797236bba7

Change-Id: I4103541d99fe59bfcf12379a1298a0a690497846

Change-Id: Ic7d2cbb2c1b2deaa4e735484bdc7413c0b3b1939

Change-Id: I866488a47ca04ca587e805663dfd597bb7b1ebce

Bug: 8636060
Change-Id: Id87b0ac4a99ec6a26db6e250d6cd22defc02a23d

Um... this is not async ? Remove that from the name

Bug: 8636060
Change-Id: Ida5f9bd6929eae75103eb2e3fb866ed7468af806

No need to test multiple times for this. Let's just never do useless
stuff, and only test for that once.

Bug: 8636060
Change-Id: I50a9e4da769fbec44fbb12eedfed03aad924cc2c

Bug: 12297051
Change-Id: Iffa1c98b8fe2b816c3ac6bc171037288107f637d

Bug: 12179576
Change-Id: I93037ee2aa7c0432400fe2f93fb60d2e60f70f5f

Change-Id: I0b3a6cdf49038c32194413c21da824784a53f581

For edit tasks, the estimate is actually the right thing to use.
This is really dangerous, but it will get rid of pretty much all
race conditions.

Change-Id: I2d5ca3ce45e32f1bd9c8b778421fd54b9c1f6f63

This just mirrors what InputLogic#tryFixLyingCursorPosition
is doing. That method will go away in the next change.

Change-Id: Ifa2827dbc1f1d20e2c642d6f2d23514a01ed9203

Bug: 12397228
Change-Id: I7632931f0685fc8f0558946be66025b2bb2b5a3d

Change-Id: I174c50f509ed6998b755e1a712e7f6c0f82f4425

This reverts commit 8bc42779.

Change-Id: I34f509998afdb1a7c120fbfdb9f0a1b188224a4d

Don't use absolute cursor positions when making edits,
this leads to race conditions.
This is a bit ugly and will need to be fixed soon. Plans are
underway to clean this up.

Bug: 12390573
Change-Id: I69c09fc41b979880d0800c55a710e39373287cff

This is conflicting with later changes. Temporary revert for cherry-pick.

This reverts commit 0b593ce8.

Change-Id: Id53eadb023a950cfcca496c0cfbfe583c7ec7b8c

Conflicts prevent this to be cherry-picked.

This reverts commit dd3d697a.

Change-Id: Ib97fae2234633b4bb27d611f48a79060db9ab16f

Don't use absolute cursor positions when making edits,
this leads to race conditions.
This is a bit ugly and will need to be fixed soon. Plans are
underway to clean this up.

Bug: 12390573
Change-Id: Ib42d4149343c642b1b5c1937b424e8afdbd4cc1f

This reverts commit 38401272.

Change-Id: I7f0d975ec9e18d94fe3505250360c2b79ccbe96d

Bug: 12179576
Change-Id: Ibafd824a0ea2251843b388e95dcbd8f9bca92d5c

This reverts commit 42e83c7f.

Bug: 12434783
Change-Id: Id01b6d14906430b13e64f5fc4d7fb01572d0a960

Don't use absolute cursor positions, this leads to race
conditions.

Bug: 12390573
Change-Id: I6f04f07a46babbc3d51cb94c7eaee21bed242396

This old method doesn't even re-read the old suggestions. It used to
recompute them without the coordinates.
Re-using the recorrection code, which is much more advanced, is
the right thing to do here.

Also, refining the test. It's no use trying to resume suggestion
if we don't have a suggestion strip, since we aren't going to
auto-correct anything anyway.

Not the motivation for this change, but this also fixes
Bug: 11620256
Change-Id: Id49efa32e293c49837c61fdc752c86bbac1d2c88

Bug: 8636060
Change-Id: Ifa027de465a421b67897d51e9ad47666dda117ad

...at last

Bug: 8636060
Change-Id: If5e27a9d28ff64d318dd76792f55edfc8a78d2d7

Bug: 8636060
Change-Id: Ie5027512f066d9c530a686ac559e4649a39bf439

Bug: 8636060
Change-Id: Idfabf7231a80e21786ce1910b5140bb3dddcac7d

This sheds some light on what's happening here. Some
comments were at least misleading, maybe indicating something
is not sequenced as intended.

Bug: 8636060
Change-Id: Ia74feb457a39fe4a672c27fe4203264fda940f04

Bug: 12295276
Change-Id: Id359c92acde44758b12929e7bac719d5c9c7577b

Bug: 12295276
Change-Id: I187016b59213d351c943c6e0b9a2ad3708499646