summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/accessibility/svg-mouse-listener.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/accessibility/svg-mouse-listener.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/accessibility/svg-mouse-listener.html')
-rw-r--r--testing/web-platform/tests/accessibility/svg-mouse-listener.html34
1 files changed, 34 insertions, 0 deletions
diff --git a/testing/web-platform/tests/accessibility/svg-mouse-listener.html b/testing/web-platform/tests/accessibility/svg-mouse-listener.html
new file mode 100644
index 0000000000..e2ca983d00
--- /dev/null
+++ b/testing/web-platform/tests/accessibility/svg-mouse-listener.html
@@ -0,0 +1,34 @@
+<!DOCTYPE html>
+<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>
+<svg viewBox="0 0 500 500">
+ <rect width="500" height="500" id="target" fill="red">
+</svg>
+
+<script>
+function clickPromise() {
+ return new Promise(resolve => {
+ document.getElementById("target").addEventListener("click", resolve,
+ { once: true });
+ });
+}
+
+// While the other accessibility tests are crash-tests, this one cannot be
+// authored as one. The reason is that a crash-test is complete when a onload
+// is complete. The recommended strategy for supporting asynchronous testing
+// is to use reftest wait. Unfortunately, reftests are not compatible with
+// test-driver. The test needs to be asynchronous as unless we wait for the
+// click to be handled, we are not giving the browser a chance to crash. In
+// addition the lack of a wait triggers detection of a memory leak in Blink.
+promise_test(async () => {
+ const click_promise = clickPromise();
+ await test_driver.click(document.body);
+ return click_promise;
+}, 'Clicking SVG element does not crash the browser');
+
+</script>
+</html>