gecko-dev/testing/web-platform/tests/fullscreen/api/element-request-fullscreen-options.html
Philip Jägenstedt d7a171e83a Bug 1488490 [wpt PR 12828] - Add basic test for requestFullscreen({ navigationUI }), a=testonly
Automatic update from web-platform-testsAdd basic test for requestFullscreen({ navigationUI }) (#12828)

Follows https://github.com/whatwg/fullscreen/pull/129.

--

wpt-commits: 880ceceec4d092bcee036a8d9dfa0181ffe468a7
wpt-pr: 12828

--HG--
extra : rebase_source : 7ccec9192e57933cdd6da2adafb91ad563adcf39
extra : source : e227ddece3f6105ddd018b2c2043061c14b584d9
2018-09-13 02:58:18 +00:00

18 lines
729 B
HTML

<!DOCTYPE html>
<title>Element#requestFullscreen({ navigationUI }) support</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<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.)
test(() => {
let invoked = false;
document.body.requestFullscreen({
get navigationUI() { invoked = true; return "irrelevant-value"; }
});
assert_true(invoked, "navigationUI getter invoked");
});
</script>