Source/web/tests/data/advance_focus_in_form_with_key_event_listeners.html - Issue 1303123002: Revert of Adding support for Smart GO NEXT feature in Android Chrome

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: Source/web/tests/data/advance_focus_in_form_with_key_event_listeners.html

Issue 1303123002: Revert of Adding support for Smart GO NEXT feature in Android Chrome (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Remove DocumentMarkerController.h include Created 5 years, 4 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « Source/web/tests/data/advance_focus_in_form_with_disabled_and_readonly_elements.html ('k') | Source/web/tests/data/advance_focus_in_form_with_tabindex_elements.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
	(Empty)
1 <html>

2 <body>

3 <!-- If any of these form element can handle key event, software keyboard should show ENTER key

4 instead of GO key, for textarea element it's exceptional, as it requires EN TER key by default

5 for enabling multiline inputs. (This will be determined from Chromium layer )" -->

6 <h3>form1 starts here</h3>

7 <form id="form1">

8 <input type="text" id="input1" form="form1" value="input1 from form1"><br>

9 <button type="button" id="button1" form="form1">button1 from form1</button><br >

10 <div id="contenteditable1" contenteditable="true">contenteditable1 from form1< /div><br>

11 <div id="div1" onkeypress="alert('if key event is handled, software keyboard s hould show ENTER key instead of GO key');"><br>

12 <input type="text" id="input2" value="input2 from div1 form1"><br>

13 </div>

14 <a href="#" id="anchor1">anchor1 from form1</a><br>

15 <textarea id="textarea1">textarea1 from form1</textarea><br>

16 <input type="text" id="input3" value="input3 from form1"><br>

17 </form>

18 <h3>form1 ends here</h3>

19 <textarea id="textarea2" form="form1">textarea2 from form1, which is outside par ent hierarchy</textarea><br>

20 <textarea id="textarea3">textarea3 neither from form1 nor from form2</textarea>< br>

21 <button type="button" id="button2" form="form1">button2 from form1, which is out side parent hierarchy, but can't navigate due to non-editable element</button><b r>

22 <div id="contenteditable2" contenteditable="true">contenteditable2 neither from form1 nor from form2</div><br>

23 <textarea id="textarea4" form="formInvalid">textarea4 neither from form1 nor fro m form2, form attribute is invalid</textarea><br>

24 <h3>form2 starts here</h3><br>

25 <form id="form2" onkeypress="alert('if key event is handled, software keyboard s hould show ENTER key instead of GO key');">

26 <textarea id="textarea5">textarea5 from form2</textarea><br>

27 <input type="text" id="input4" value="input4 from form2"><br>

28 <div id="contenteditable3" contenteditable="true">contenteditable3 from form2< /div><br>

29 <a href="#" id="anchor2">anchor2 from form2</a><br>

30 </form>

31 <h3>form2 ends here</h3><br>

32 </body>

33 </html>

OLD	NEW