Test that element.requestFullscreen() consumes user activation (web-p…

…latform-tests#36969)
BruceDai · Dec 13, 2022 · 976ac1b · 976ac1b
1 parent 4de30b6
commit 976ac1b
Show file tree

Hide file tree

Showing 9 changed files with 52 additions and 309 deletions.
diff --git a/fullscreen/api/element-request-fullscreen-consume-user-activation.html b/fullscreen/api/element-request-fullscreen-consume-user-activation.html
@@ -0,0 +1,25 @@
+<!DOCTYPE html>
+<title>Element#requestFullscreen() consumes user activation</title>
+<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>
+<div id="log"></div>
+<script>
+promise_test(async (t) => {
+    t.add_cleanup(() => {
+        if (document.fullscreenElement) return document.exitFullscreen();
+    });
+    const div = document.querySelector("div");
+
+    await test_driver.bless("fullscreen");
+    assert_true(navigator.userActivation.isActive, "Activation must be active");
+    // Request fullscreen twice in a row. The first request should consume the
+    // user activation and succeed, and the second request should fail because
+    // of the user activation requirement.
+    const p1 = div.requestFullscreen();
+    assert_false(navigator.userActivation.isActive, "Transient activation is consumed");
+    const p2 = promise_rejects_js(t, TypeError, div.requestFullscreen());
+    await Promise.all([p1, p2]);
+});
+</script>
diff --git a/fullscreen/api/element-request-fullscreen-same-element.html b/fullscreen/api/element-request-fullscreen-same-element.html
@@ -0,0 +1,27 @@
+<!DOCTYPE html>
+<title>Element#requestFullscreen() on the current fullscreen element</title>
+<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>
+<div id="log"></div>
+<script>
+promise_test(async (t) => {
+    t.add_cleanup(() => {
+        if (document.fullscreenElement) return document.exitFullscreen();
+    });
+
+    // Use the body element as the fullscreen element, because the second
+    // test_driver.bless() call needs to insert a button inside of it, which
+    // can't be clicked if another element is already fullscreen.
+    const target = document.body;
+
+    // First enter fullscreen.
+    await test_driver.bless("fullscreen", () => target.requestFullscreen());
+    assert_equals(document.fullscreenElement, target, "fullscreen element after first request");
+
+    // Now request fullscreen again, which should be a no-op.
+    await test_driver.bless("fullscreen", () => target.requestFullscreen());
+    assert_equals(document.fullscreenElement, target, "fullscreen element after second request");
+});
+</script>
diff --git a/fullscreen/api/element-request-fullscreen-same-manual.html b/fullscreen/api/element-request-fullscreen-same-manual.html
diff --git a/fullscreen/api/element-request-fullscreen-twice-manual.html b/fullscreen/api/element-request-fullscreen-twice-manual.html
diff --git a/fullscreen/api/element-request-fullscreen-twice-manual.tentative.html b/fullscreen/api/element-request-fullscreen-twice-manual.tentative.html
diff --git a/fullscreen/api/element-request-fullscreen-two-elements-manual.html b/fullscreen/api/element-request-fullscreen-two-elements-manual.html
diff --git a/fullscreen/api/element-request-fullscreen-two-elements-manual.tentative.html b/fullscreen/api/element-request-fullscreen-two-elements-manual.tentative.html
diff --git a/fullscreen/api/element-request-fullscreen-two-iframes-manual.html b/fullscreen/api/element-request-fullscreen-two-iframes-manual.html
diff --git a/fullscreen/api/element-request-fullscreen-two-iframes-manual.tentative.html b/fullscreen/api/element-request-fullscreen-two-iframes-manual.tentative.html