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

Unified 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 side-by-side diff with in-line comments

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 »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: Source/web/tests/data/advance_focus_in_form_with_key_event_listeners.html

diff --git a/Source/web/tests/data/advance_focus_in_form_with_key_event_listeners.html b/Source/web/tests/data/advance_focus_in_form_with_key_event_listeners.html

deleted file mode 100644

index 3efa61f1bfc2a090e0786f6b17f123e7b5ad9520..0000000000000000000000000000000000000000

--- a/Source/web/tests/data/advance_focus_in_form_with_key_event_listeners.html

+++ /dev/null

@@ -1,33 +0,0 @@

-<html>

-<body>

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

- instead of GO key, for textarea element it's exceptional, as it requires ENTER key by default

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

-<h3>form1 starts here</h3>

-<form id="form1">

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

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

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

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

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

- </div>

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

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

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

-</form>

-<h3>form1 ends here</h3>

-<textarea id="textarea2" form="form1">textarea2 from form1, which is outside parent hierarchy</textarea><br>

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

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

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

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

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

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

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

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

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

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

-</form>

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

-</body>

-</html>