summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/close-watcher/user-activation/nn-activate-dialog.html
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 01:14:29 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 01:14:29 +0000
commitfbaf0bb26397aa498eb9156f06d5a6fe34dd7dd8 (patch)
tree4c1ccaf5486d4f2009f9a338a98a83e886e29c97 /testing/web-platform/tests/close-watcher/user-activation/nn-activate-dialog.html
parentReleasing progress-linux version 124.0.1-1~progress7.99u1. (diff)
downloadfirefox-fbaf0bb26397aa498eb9156f06d5a6fe34dd7dd8.tar.xz
firefox-fbaf0bb26397aa498eb9156f06d5a6fe34dd7dd8.zip
Merging upstream version 125.0.1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'testing/web-platform/tests/close-watcher/user-activation/nn-activate-dialog.html')
-rw-r--r--testing/web-platform/tests/close-watcher/user-activation/nn-activate-dialog.html40
1 files changed, 40 insertions, 0 deletions
diff --git a/testing/web-platform/tests/close-watcher/user-activation/nn-activate-dialog.html b/testing/web-platform/tests/close-watcher/user-activation/nn-activate-dialog.html
new file mode 100644
index 0000000000..5cc866044c
--- /dev/null
+++ b/testing/web-platform/tests/close-watcher/user-activation/nn-activate-dialog.html
@@ -0,0 +1,40 @@
+<!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="/common/top-layer.js"></script>
+<script src="../resources/helpers.js"></script>
+
+<!--
+ This test has different expectations for dialogs vs. CloseWatchers because
+ dialogs queue a task to fire their close event, and do not do so for their
+ cancel event. Thus, when you have two dialogs grouped together, you get the
+ somewhat-strange behavior of both cancels firing first, then both closes.
+ Whereas CloseWatchers do not have this issue; both fire synchronously.
+
+ Note that scheduling the cancel event for dialogs is not really possible since
+ it would then fire after the dialog has been closed in the DOM and visually.
+ So the only reasonable fix for this would be to stop scheduling the close
+ event for dialogs. That's risky from a compat standpoint, so for now, test the
+ strange behavior.
+-->
+
+<body>
+<script>
+const type = "dialog";
+
+promise_test(async t => {
+ const events = [];
+
+ createRecordingCloseWatcher(t, events, "watcher1", type);
+ const watcher2 = createRecordingCloseWatcher(t, events, "watcher2", type);
+
+ await maybeTopLayerBless(watcher2);
+
+ await sendCloseRequest();
+ await waitForPotentialCloseEvent();
+ assert_array_equals(events, ["watcher2 cancel", "watcher1 cancel", "watcher2 close", "watcher1 close"]);
+}, "Create two dialogs without user activation; send user activation");
+</script>