[Android] Adding Smart GO/NEXT feature in Chrome

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 edf7101d03a303cd8b575a15d08d6ac4c4517249..17d6f174f92d551011bfb92b0e96c86118505359 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
@@ -39,6 +39,9 @@ import java.util.concurrent.Callable;
  */
 @RunWith(ContentJUnit4ClassRunner.class)
 public class ImeTest {
+    private static final int DEFAULT_IME_OPTIONS =
+            EditorInfo.IME_FLAG_NO_FULLSCREEN | EditorInfo.IME_FLAG_NO_EXTRACT_UI;

[Changwan Ryu, 2017/05/09 18:12:16]

Instead of make another dependency on the production logic, how about adding
IME_ACTION_MASKS = EditorInfo.IME_ACTION_NEXT | EditorInfo.IME_ACTION_PREVIOUS |
EditorInfo.IME_ACTION_GO

and using & operator to check the final value against expected value?

[AKVT, 2017/05/10 09:31:38]

Done. That seems to be more easier.

+
     @Rule
     public ImeActivityTestRule mRule = new ImeActivityTestRule();
 
@@ -418,6 +421,26 @@ public class ImeTest {
 
     @Test
     @SmallTest
+    @Feature({"TextInput", "Main"})
+    public void testAdvanceFocusNextAndPrevious() throws Exception {
+        DOMUtils.clickNode(mRule.getContentViewCore(), "input_text");
+        mRule.assertWaitForKeyboardStatus(true);
+        Assert.assertEquals(DEFAULT_IME_OPTIONS | EditorInfo.IME_ACTION_NEXT,

[AKVT, 2017/05/09 17:22:18]

I am seeing a failure in this line. As per the logic it supposed to be 
DEFAULT_IME_OPTIONS | EditorInfo.IME_ACTION_NEXT

And visually also it's correctly appearing on IME

But test is failing as it's coming with DEFAULT_IME_OPTIONS |
EditorInfo.IME_ACTION_NONE.

[Changwan Ryu, 2017/05/09 18:12:16]

My initial guess is that assertWaitForKeyboardStatus(true) isn't actually
waiting for anything since keyboard is already showing from setUp().
It takes a round trip to the renderer process for the click event to restart /
show input.

You'd consider calling mRule.focusElement("input_text") which should wait for
states to be correctly updated.

[AKVT, 2017/05/10 09:31:38]

Thanks. I corrected it using mRule.focusElement();

+                mRule.getInputMethodManagerWrapper().getImeOptions());
+
+        // Forward direction focus
+        mRule.performEditorAction(EditorInfo.IME_ACTION_NEXT);
+        Assert.assertEquals(DEFAULT_IME_OPTIONS | EditorInfo.IME_ACTION_NONE,
+                mRule.getInputMethodManagerWrapper().getImeOptions());
+        mRule.performEditorAction(EditorInfo.IME_ACTION_NEXT);
+        // Now we have reached the last element of the form, hence focus won't change after issuing
+        // NEXT.
+        Assert.assertEquals(DEFAULT_IME_OPTIONS | EditorInfo.IME_ACTION_NONE,
+                mRule.getInputMethodManagerWrapper().getImeOptions());
+    }
+
+    @Test
+    @SmallTest
     @DisabledTest(message = "crbug.com/694812")
     @Feature({"TextInput"})
     public void testShowAndHideSoftInput() throws Exception {