summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/fullscreen/api/element-request-fullscreen-options.html
blob: c11f54f7b5ba1fd22a91ec093cc5b7a47938165f (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
<!DOCTYPE html>
<title>Element#requestFullscreen({ navigationUI }) support</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<body></body>
<script>
    // Tests for https://github.com/whatwg/fullscreen/pull/129. Because there are
    // no normative requirements on what navigationUI should do, just test for
    // basic support. (One could also check that the three allowed enum valid are
    // supported and no others, but that would overlap with UA-specific tests.)
    promise_test(async (t) => {
        const invalidDict = {
            get navigationUI() {
                return "invalid-value";
            },
        };
        await promise_rejects_js(
            t,
            TypeError,
            document.body.requestFullscreen(invalidDict)
        );
        await promise_rejects_js(
            t,
            TypeError,
            document.body.requestFullscreen({ navigationUI: "other-invalid-value" })
        );
    }, "requestFullscreen() with invalid navigationUI values");
</script>