Change-Id: I1061da0edfdb05c64c5711717d4ef9fa9681e568

Bug: 6785706
Change-Id: Ic7bf242ef058d116b986d47ad197b6d2802e2342

Change-Id: I7c16e28ffce4fe0965b756bf2b00ee63b77dd039

If the separator is not a space, then we will always call
setPunctuationSuggestions and reset the suggestion strip anyway.
If the separator is a space, then the cursor has a space on
the left, which means isCursorTouchingWord depends only on
whether it touches a word on the right. If we were displaying
the "add to dictionary hint", it means a suggestion was just
chosen, so it had to be displayed, and that requires a composing
word and no non-separator at the right of the cursor.

In the end, if we go through this postUpdateSuggestions call,
we are sure we will reset the suggestions later in this method,
either by calling postUpdateBigramPredictions, or
setPunctuationSuggestions.

Change-Id: I95d5f77a5d0ac6d1a6ced8d67d6ac8f650db4a32

Change-Id: I606270a0387787445b7cd6b94e4830bfc144b49e

This reverts commit 48a43608.

Change-Id: Iff324c705b46cfae27ea9b6b8dc8b0a0d56a193d

Change-Id: I117e2429c5f5e75a6ffe84b5869afb2e033f2b2d

Just after this, clear() will be called, removing the suggestion
strip from the screen. It will later be displayed again through
onStartInputView, which will update its content.

Change-Id: I15c23ad2adecab76b0791d7fc222d15b6533f3bd

Change-Id: I99e912d3edfc7dd3f17ee835331d5fcba976750c

The responsivity is better like this. This does not seem to
feel slow as the previous comment seemed to indicate.

Also remove a stale comment.

Change-Id: I4e7bf9fe28716e112db182e44b3fa88ee4526bb4

After reverting an auto-correct we always have a separator after
the previously inserted word, and the cursor is never touching
a word. Showing predictions is the right thing to do, while
calling postUpdateSuggestions will invariably yield an invariably
blank suggestion strip, which is not very helpful.

Likewise, after we pick a suggestion, we should be showing the
predictions unless showing the addToDictionary hint. There was
a bug here in the corner case that the word would be a candidate
for user dictionary, but the user dictionary provider is not
available: in this case we should be showing predictions, but
we were showing an unhelpful empty suggestion bar.

Change-Id: I287bb5eb4af762bd5a433e85e185fab6d203e91a

We stopped cancelling manual picks a few weeks ago. This code
is dead.

Change-Id: I4032fcc3c95e9379f1839fe860a1b8a9bd7d0bc7

Bug: 6766059
Change-Id: I378f9d35c4904c4f373260bda5863235d833eb31

If suggestion and prediction messages both happen to be in
the queue, the latest one will win (update the suggestion strip
later than the other, overwriting any previous suggestions).
So when we enqueue either one, it is always safe to cancel
all messages of both types.

Change-Id: Iad9dd06d08c49f60cac16b88edcc9531a18ec02e

Change-Id: I9974b88923b85cd6bec74f7607067c660f36f040

Bug: 6781106
Change-Id: I22f04af4fabf93346ab6f72c1841f096afaccb96

Change-Id: If36b5375b04f68deeb72bcece3cb8d37aed57f59

Change-Id: If711074fdcb586e35d02e421c845f2c9024ca718

Change-Id: I56bc5b9b584de5a14b41fc32c19f7fefb3b12e88

Change-Id: If1589e29728df20713c75e08df7f47f0de9202d4

Change-Id: I0b62098308169b5c44ced25ffb902766e3732fbf

Also add some comment to clarify what's happening inside those
methods

Change-Id: I5b9b1e105b3145f0b050f35d12c5b6ca6e4a4d8c