File: element-ready-check-fullscreen-iframe-child-manual.html

package info (click to toggle)
thunderbird 1%3A52.8.0-1~deb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 1,710,120 kB
  • sloc: cpp: 5,081,109; ansic: 2,051,982; python: 458,727; java: 241,615; xml: 193,367; asm: 178,649; sh: 81,881; makefile: 24,703; perl: 16,874; objc: 4,389; yacc: 1,816; ada: 1,697; lex: 1,257; pascal: 1,251; cs: 879; exp: 499; php: 436; lisp: 258; awk: 152; sed: 51; ruby: 47; csh: 27
file content (28 lines) | stat: -rw-r--r-- 1,213 bytes parent folder | download | duplicates (4) 
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 ready check for child of a fullscreen iframe</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="../trusted-click.js"></script>
<div id="log"></div>
<iframe><!-- script inserts div here --></iframe>
<script>
// Verify that an iframe can itself go fullscreen, and that this doesn't
// influence the iframe ancestor test of the element ready check.
async_test(function(t)
{
    var iframe = document.querySelector("iframe");
    document.onfullscreenchange = t.step_func(function()
    {
        assert_equals(document.fullscreenElement, iframe, "fullscreen element");
        var div = document.createElement("div");
        // This adds the div to the iframe element itself, not to the iframe's
        // contentDocument. It's done here because the HTML parser treats the
        // content of iframe as a text node.
        iframe.appendChild(div);
        trusted_request(div, iframe.contentDocument.body);
        document.onfullscreenchange = t.unreached_func("second fullscreenchange event");
        document.onfullscreenerror = t.step_func_done();
    });
    trusted_request(iframe);
});
</script>