remote-context-executor.https.html | Explore in Territory

<!DOCTYPE html>
<script src="/resources/testharness.js"></script>
<script src="utils.js"></script>
<script src="/common/dispatcher/dispatcher.js"></script>
<script src="/common/get-host-info.sub.js"></script>
<script src="/common/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="/attribution-reporting/resources/helpers.js"></script>
<title>Script to wait for instructions from RemoteContext.</title>

<body>
<script>
window.addEventListener("load", async () => {
  // Find the uuid to communicate with the parent.
  const uuid = new URLSearchParams(window.location.search).get('uuid');

  // Wait for the window to have its size computed and become visible,
  // so that simulated user gestures will be handled properly.
  while (window.innerWidth == 0) {
    await new Promise(resolve => requestAnimationFrame(resolve));
  }

  // Exempt the remote context dispatch server from network revocation,
  // so that you can continue to control fenced frames after network is
  // disabled.
  const remote_context_dispatcher_url = dispatcher_url + `?uuid=${uuid}`;
  await window.internals.exemptUrlFromNetworkRevocation(
      remote_context_dispatcher_url);

  // Create a RemoteContext Executor, which will wait in the background
  // for scripts to execute.
  window.executor = new Executor(uuid);
});
</script>
</body>

chromium/third_party/blink/web_tests/wpt_internal/fenced_frame/resources/remote-context-executor.https.html