write-on-detaching-iframe.https.html

Enable keyboard shortcuts

This WPT test may be referenced by the following Test IDs:
- /clipboard-apis/detached-iframe/write-on-detaching-iframe.https.html - WPT Dashboard Interop Dashboard

<!doctype html>

<meta charset=utf-8>

<title>navigator.clipboard write on detaching iframe</title>

<link rel='help' href='https://w3c.github.io/clipboard-apis/#async-clipboard-api'>

<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/user-activation.js"></script>

<iframe id="iframe"></iframe>

<script>

'use strict';

promise_test(async t => {

  // This tests proper behavior on a detaching iframe. text/plain is chosen for

  // simplicity, and the test should fail the same way no matter what the input

  // type is.

  await tryGrantReadPermission();

  await tryGrantWritePermission();

  const iframe = document.getElementById('iframe');

  const iframeClipboard = iframe.contentWindow.navigator.clipboard;

  const blobInput = new Blob(['test string'], {type: 'text/plain'});

  const clipboardItemInput = new ClipboardItem({'text/plain': blobInput});

  // Clipboard API must only be available in focused documents.

  // reference: https://www.w3.org/TR/clipboard-apis/#privacy-async

  iframe.focus();

  // An iframe detaching while writing to the clipboard should fail, but not

  // crash. The lack of await here means that the iframe will detach while the

  // write operation is running.

  iframeClipboard.write([clipboardItemInput]);

  iframe.parentNode.removeChild(iframe);

}, 'Verify write fails on detaching iframe');

</script>