File: element-request-fullscreen-options.html

package info (click to toggle)
thunderbird 1%3A140.4.0esr-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 4,609,432 kB
  • sloc: cpp: 7,672,442; javascript: 5,901,613; ansic: 3,898,954; python: 1,413,343; xml: 653,997; asm: 462,286; java: 180,927; sh: 113,489; makefile: 20,460; perl: 14,288; objc: 13,059; yacc: 4,583; pascal: 3,352; lex: 1,720; ruby: 1,222; exp: 762; sql: 715; awk: 580; php: 436; lisp: 430; sed: 70; csh: 10
file content (28 lines) | stat: -rw-r--r-- 1,078 bytes parent folder | download | duplicates (18) 
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>