1 files changed, 0 insertions, 32 deletions
diff --git a/testing/web-platform/tests/close-watcher/user-activation-multiple-plus-free.html b/testing/web-platform/tests/close-watcher/user-activation-multiple-plus-free.html
deleted file mode 100644
index a94b47904a..0000000000
--- a/testing/web-platform/tests/close-watcher/user-activation-multiple-plus-free.html
+++ /dev/null
@@ -1,32 +0,0 @@
-<!doctype html>
-<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/testdriver-actions.js"></script>
-<script src="resources/helpers.js"></script>
-
-<body>
-<script>
-
-// This test needs to be separate from user-activation.html since, unlike those,
-// it relies on there not being any lingering user activation from previous
-// tests hanging around. That is, we need to be sure freeWatcher is created with
-// no user activation, to ensure that activationWatcher1 and activationWatcher2
-// get grouped as expected.
-promise_test(async t => {
-  const events = [];
-  createRecordingCloseWatcher(t, events, "freeWatcher");
-
-  await test_driver.bless("create two more CloseWatchers", () => {
-    createRecordingCloseWatcher(t, events, "activationWatcher1");
-    createRecordingCloseWatcher(t, events, "activationWatcher2");
-  });
-
-  await sendCloseRequest();
-  assert_array_equals(events, ["activationWatcher2 close", "activationWatcher1 close"]);
-
-  await sendCloseRequest();
-  assert_array_equals(events, ["activationWatcher2 close", "activationWatcher1 close", "freeWatcher close"]);
-}, "Multiple CloseWatchers created from a single user activation close together, but original free CloseWatcher closes separately");
-</script>