summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/fenced-frame/resources/navigate-ancestor-from-nested-fenced-frame.https.html
blob: 74800b969f772c9aecb186a29f51f3ceaef2cd16 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
<!DOCTYPE html>
<title>Navigate ancestor helper</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="utils.js"></script>

<body>
<script>
(async () => {
  // This document is loaded into a fenced frame by
  // `navigate-ancestor-test-runner.https.html`. It creates a nested fenced
  // frame and navigates it to `navigate-ancestor-helper.https.html`.

  // - navigate_ancestor_key:
  // Sent by `navigate-ancestor-destination.https.html`. We listen to it, and
  // report back to our embedder that it loaded correctly and did not navigate
  // *this* frame.
  // - navigate_ancestor_from_nested_key:
  // Sent by us to our embedder to indicate (depending on the message) either:
  //   - PASS: The nested fenced frame was navigated correctly when it tried to
  //           navigate its ancestor (parent or top) frame
  //   - FAIL: When the nested fenced frame tried to navigate its ancestor
  //           frame, it actually navigated *this frame*, which is wrong
  const [navigate_ancestor_key, navigate_ancestor_from_nested_key,
      ancestor_type] = parseKeylist();

  window.onbeforeunload = e => {
    writeValueToServer(navigate_ancestor_from_nested_key,
                       `FAIL nested fenced frame ${ancestor_type}`);
  }

  attachFencedFrame(generateURL(`navigate-ancestor-helper.https.html`,
      [navigate_ancestor_key, ancestor_type]));
  await nextValueFromServer(navigate_ancestor_key);
  window.onbeforeunload = null;
  writeValueToServer(navigate_ancestor_from_nested_key, "PASS");
})();
</script>
</body>