gecko-dev/testing/web-platform/tests/fullscreen/api/element-request-fullscreen-two-iframes-manual.html
Sergio Villar Senin 20e6065a94 Bug 1532639 [wpt PR 15630] - Add <meta name=timeout content=long> to WPT in SlowTests, a=testonly
Automatic update from web-platform-tests
Add <meta name=timeout content=long> to WPT in SlowTests

This is the 2nd step in the process of banning external/wpt from
SlowTests. After cleaning up the wtp entries we're marking them as
slow by using wpt idioms, i.e.:

1) Add <meta name="timeout" content="long"> to .html files
2) Add // META: timeout=long to .js files

Bug: 765026
Change-Id: Iaf051104f419524916e19324996cc36ee37d5426
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497005
Commit-Queue: Sergio Villar <svillar@igalia.com>
Reviewed-by: Andy Paicu <andypaicu@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#643402}

--

wpt-commits: 7287608f90f6b9530635d10086fd2ab386faab38
wpt-pr: 15630
2019-04-24 11:19:30 +01:00

48 lines
1.8 KiB
HTML

<!DOCTYPE html>
<title>Element#requestFullscreen() on two elements in different iframes</title>
<meta name="timeout" content="long">
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="../trusted-click.js"></script>
<div id="log"></div>
<iframe id="a" allowfullscreen></iframe>
<iframe id="b" allowfullscreen></iframe>
<script>
async_test(t => {
// Request fullscreen on the body elements of both iframes, but in reverse
// tree order.
const a = document.getElementById('a');
const b = document.getElementById('b');
// Expect two fullscreenchange events, with document.fullscreenElement
// changing in the same order as the requests. (Events should also fire on the
// iframes' documents, but this is not covered by this test.)
const order = [];
document.onfullscreenchange = t.step_func(() => {
assert_in_array(document.fullscreenElement, [a, b]);
order.push(document.fullscreenElement.id);
if (order.length == 2) {
// When the second event arrived, the fullscreen element may still be the
// old one.
//
// TODO(mustaq): We need a better explanation here to cover the tree-order
// idea of the spec.
assert_true(order[0] == 'a' || order[0] == 'b', 'first id seen is a or b');
assert_true(order[1] == 'a', 'second id seen is a');
t.done();
}
});
document.onfullscreenerror = t.unreached_func('fullscreenerror event');
// Make a trusted click on frame 'b' to activate it.
trusted_click(t, () => {
// Now queue a trusted click on frame 'a' to make back-to-back calls.
setTimeout(() => {
trusted_click(t, () => {
b.contentDocument.body.requestFullscreen();
a.contentDocument.body.requestFullscreen();
}, a.contentDocument.body);
}, 0);
}, b.contentDocument.body);
});
</script>