fenced-frame/automatic-beacon-data-cross-origin-ancestor.sub.https.html

<!DOCTYPE html>
<title>Test window.fence.setReportEventDataForAutomaticBeacons</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="/common/utils.js"></script>
<script src="/common/dispatcher/dispatcher.js"></script>
<script src="resources/utils.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/get-host-info.sub.js"></script>
<script src="resources/automatic-beacon-helper.js"></script>

<body>
<script>
promise_test(async(t) => {
  // This test creates the following frame tree:
  // Root Frame (A)
  //  └─Fenced Frame (A)
  //     └─IFrame (B) [sets data]
  //        └─IFrame (C) [performs navigation]
  // It then checks that C's navigation uses the data set in B, even if B is
  // cross-origin to fencedframe A.
  const fencedframe = await attachFencedFrameContext({
    generator_api: 'fledge', register_beacon: true
  });

  const beacon = {
    eventType: "reserved.top_navigation_start",
    eventData: "This is the start data",
    destination: ["buyer"],
    crossOriginExposed: true
  }

  await fencedframe.execute(async (beacon) => {
    const iframe = await attachIFrameContext({
      origin: 'https://{{hosts[][www2]}}:{{ports[https][1]}}'
    });
    // IFrame (C) is created during this setupAutomaticBeacon() call. The data
    // for IFrame (B) is also set during this call.
    return setupAutomaticBeacon(iframe, [beacon],
        "resources/close.html", NavigationTrigger.CrossOriginClick,
        "_blank");
  }, [beacon]);

  await multiClick(10, 10, fencedframe.element)

  await verifyBeaconData(beacon.eventType, beacon.eventData,
      get_host_info().HTTPS_REMOTE_ORIGIN);
}, 'An automatic beacon can use data set by a cross-origin ancestor.');

</script>
</body>