summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/fullscreen/api/element-request-fullscreen-active-document.html
blob: bac8631059002902b6222a740a07d625e71bb995 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
<!DOCTYPE html>
<title>
    Element#requestFullscreen() when the document is not the active document
</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<div id="log"></div>
<iframe allowfullscreen></iframe>
<script>
    promise_test(async (t) => {
        const iframe = document.querySelector("iframe");
        const typeErrorConstructor = iframe.contentWindow.TypeError;
        const documentBeforeNav = iframe.contentDocument;

        documentBeforeNav.onfullscreenchange = t.unreached_func(
            "fullscreenchange event"
        );
        documentBeforeNav.onfullscreenerror = t.unreached_func(
            "fullscreenerror event"
        );

        await new Promise((r) => {
            iframe.src = "/common/blank.html";
            iframe.onload = r;
        });

        await promise_rejects_js(
            t,
            typeErrorConstructor,
            documentBeforeNav.documentElement.requestFullscreen()
        );

        // Per spec the fullscreenerror event should be fired at the next animation
        // frame, but at least Gecko and WebKit will instead effectively do "queue a
        // task to fire ...". Use both rAF and setTimeout to fail even if the timing
        // of the (unexpected) event isn't as expected.
        await new Promise((resolve) => {
            requestAnimationFrame(() => {
                t.step_timeout(resolve);
            });
        });
    });
</script>