element-request-fullscreen-same-element.html

Enable keyboard shortcuts

This test has a WPT meta file that expects 1 subtest issues.
This WPT test may be referenced by the following Test IDs:
- /fullscreen/api/element-request-fullscreen-same-element.html - WPT Dashboard Interop Dashboard

<!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>

<script src="../trusted-click.js"></script>

<div id="log"></div>

<script>

promise_test(async (t) => {

    t.add_cleanup(() => {

        if (document.fullscreenElement) return document.exitFullscreen();

});

    document.onfullscreenerror = t.unreached_func("fullscreenerror event");

    // 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 Promise.all([

      fullScreenChange(),

      test_driver.bless("fullscreen", () => target.requestFullscreen()),

]);

    assert_equals(document.fullscreenElement, target, "fullscreen element after first request");

    // The next requestFullscreen() should fire no events due to "If element is

    // doc's fullscreen element, terminate these subsubsteps."

    document.onfullscreenchange = t.unreached_func(

        "fullscreenchange event"

);

    // 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>