Fix some flaky IME tests caused by incorrect selection update

content/public/android/javatests/src/org/chromium/content/browser/input/ImeTest.java

Index: content/public/android/javatests/src/org/chromium/content/browser/input/ImeTest.java
diff --git a/content/public/android/javatests/src/org/chromium/content/browser/input/ImeTest.java b/content/public/android/javatests/src/org/chromium/content/browser/input/ImeTest.java
index a6f43afbe667d7bb8cf893789ee3754996deba73..78e1660a8d1c932b732f0a33181222415dca49fb 100644
--- a/content/public/android/javatests/src/org/chromium/content/browser/input/ImeTest.java
+++ b/content/public/android/javatests/src/org/chromium/content/browser/input/ImeTest.java
@@ -94,6 +94,7 @@ public class ImeTest extends ContentShellTestBase {
         waitForEventLogs("selectionchange");
         clearEventLogs();
 
+        waitAndVerifyUpdateSelection(0, 0, 0, -1, -1);

[Changwan Ryu, 2016/12/22 10:01:39]

RenderWidget::resetInputMethod() indeed calls UpdateTextInputState() *after*
initiating restart input. But normally it should be ignored unless there was
some change, in text_input_info_ or can_compose_inline_. In any case, redundant
state update should do no harm, so I agree that fixing the test should be enough
for now.

         resetAllStates();
     }