Source code
Revision control
Copy as Markdown
Other Tools
Test Info: Warnings
- This test has a WPT meta file that expects 1 subtest issues.
- This WPT test may be referenced by the following Test IDs:
- /html/interaction/focus/focusgroup/tentative/sequential-navigation/arrow-key-handler-with-priority.html - WPT Dashboard Interop Dashboard
<!DOCTYPE html>
<meta charset="utf-8">
<title>HTML Test: focusgroup - focusgroupstart on native arrow key handler</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="/resources/testdriver.js"></script>
<script src="/resources/testdriver-vendor.js"></script>
<script src="/resources/testdriver-actions.js"></script>
<script src="/shadow-dom/focus-navigation/resources/focus-utils.js"></script>
<script src="../resources/focusgroup-utils.js"></script>
<button id="before">Before</button>
<div id="toolbar" focusgroup="toolbar">
<button id="btn1">Button 1</button>
<input id="search" type="text" focusgroupstart placeholder="Search">
<button id="btn2">Button 2</button>
</div>
<button id="after">After</button>
<script>
promise_test(async t => {
const before = document.getElementById("before");
const search = document.getElementById("search");
const btn2 = document.getElementById("btn2");
const after = document.getElementById("after");
// Focus moves to search (focusgroupstart) on Tab, then Tab escape moves
// to btn2 (next adjacent item) to ensure content is not skipped while
// arrow keys are conflicting with normal focusgroup navigation.
await assert_focusgroup_tab_navigation([before, search, btn2, after]);
// Going backwards, memory of last focused item (btn2) is respected,
// and search is not considered to be in sequential tab ordering.
await assert_focusgroup_shift_tab_navigation([after, btn2, before]);
}, "Tab entry respects focusgroupstart on native arrow key handler");
</script>