navigate-ancestor-top-level-fenced-frame.https.html

Enable keyboard shortcuts

This test has a WPT meta file that expects 2 subtest issues.
This WPT test may be referenced by the following Test IDs:
- /fenced-frame/navigate-ancestor-top-level-fenced-frame.https.html - WPT Dashboard Interop Dashboard

<!DOCTYPE html>

<title>Test navigating an ancestor frame from a fenced frame</title>

<script src="/resources/testharness.js"></script>

<script src="/resources/testharnessreport.js"></script>

<script src="/resources/testdriver.js"></script>

<script src="/resources/testdriver-actions.js"></script>

<script src="/resources/testdriver-vendor.js"></script>

<script src="/common/utils.js"></script>

<script src="/common/dispatcher/dispatcher.js"></script>

<script src="/common/get-host-info.sub.js"></script>

<script src="resources/utils.js"></script>

<script src="resources/navigate-ancestor-helper.js"></script>

<body>

<script>

promise_test(async t => {

  await runNavigateAncestorTest("top-level fenced frame", "parent");

}, "Top-level fenced frames that navigate _parent end up navigating themselves");

promise_test(async t => {

  await runNavigateAncestorTest("top-level fenced frame", "top");

}, "Top-level fenced frames that navigate _top end up navigating themselves");

</script>

</body>