[Android] Adding Smart GO/NEXT feature in Chrome

content/test/data/android/input/input_forms.html

Index: content/test/data/android/input/input_forms.html
diff --git a/content/test/data/android/input/input_forms.html b/content/test/data/android/input/input_forms.html
index 55b0dadfa80310ca8fa465cd0cd99ff71f185fae..7c4cfdc71ea541863d6bf1d667a407a8ba84e65e 100644
--- a/content/test/data/android/input/input_forms.html
+++ b/content/test/data/android/input/input_forms.html
@@ -8,9 +8,6 @@
       <br/>
     </form>
     <form>
-      <br/>
-      <input id="input_radio" type="radio" style="width:50px;height:50px" />
-      <br/>
       <textarea id="textarea" rows="4" cols="20"></textarea>
       <br/>
       <textarea id="textarea2" rows="4" cols="20" autocomplete="off"></textarea>
@@ -18,7 +15,15 @@
       <input id="input_number1" type="number" /><br/>
       <input id="input_number2" type="number" /><br/>
       <br/>
-      <span id="plain_text">This is Plain Text One</span>
+      <span id="plain_text">This is Plain Text One</span><br/>
+      <br/>
+      <div id="contenteditable1" contenteditable>contenteditable1</div>
+      <br/>
+      <input id="search1" type="search" size="10" size="10"/>
+      <br/>
+      <input id="input_text1" type="text" size="10" size="10"/><br/>
+      <input id="input_radio" type="radio" style="width:50px;height:50px" /><br/>

[Changwan Ryu, 2017/06/12 20:47:24]

could you explain why and how this fixes the flakiness that you mentioned in
patch 23?

[AKVT, 2017/06/13 06:41:49]

testSelectActionBarClearedOnTappingOutsideInput() second part is clicking on the
input_radio while text selection and selection popup is active on input_text
element. The Popup is very close to input_radio element, so while processing
DomUtils.clickNode(), it's not able to focus exactly that element. Also in that
case, click is happening to some input element in the bottom of the page and IME
is not dismissing, so test goes flaky, and I observed this visual difference on
Google Pixel device, where test is not passing in first attempt, but after
maximum attempts, it's passing. Then I had a thought to keep at somewhere down,
where no way popup can interfere with element, and the issue got fixed.
But I am little clueless, why this issue only happened after I added 4 elements
in this test page. I am doubting it's an issue with DomUtils in clickNode()
operation in finding proper element.

[Changwan Ryu, 2017/06/13 15:43:27]

I see. In case things don't work out, you can also try reducing the number of
rows of the textarea and or adding another radio button at the top.

+      <br/>
     </form>
 
     <!-- We may trigger different sets of events for CONTENTEDITABLE and INPUT / TEXTAREA -->