Update web-platform-tests to revision 0fe9f012a8ee5503b728a379705a6c5286ba1e96

This commit is contained in:
WPT Sync Bot 2018-02-23 20:08:37 -05:00
parent 8329a45163
commit 5dc1649544
69 changed files with 1716 additions and 112 deletions

View file

@ -12,6 +12,8 @@ async_test(t => {
// Enter fullscreen for the iframe's body element.
trusted_request(t, iframeDoc.body, document.body);
document.onfullscreenchange = t.step_func(() => {
assert_equals(document.fullscreenElement, iframe, "document's initial fullscreen element");
assert_equals(iframeDoc.fullscreenElement, iframeDoc.body, "iframe's initial fullscreen element");
// Then, move the outer document's body into the iframe. This is an unusual
// thing to do, but means that the iframe is removed from its document and
@ -20,12 +22,15 @@ async_test(t => {
// If we exit in an orderly fashion, that's all one can ask for.
document.onfullscreenchange = t.step_func_done(() => {
assert_equals(document.fullscreenElement, null, "document's fullscreen element");
assert_equals(document.fullscreenElement, null, "document's final fullscreen element");
// the iframe's contentDocument has become undefined, but the reference
// we're holding on to should not have a fullscreen element either.
assert_equals(iframe.contentDocuemnt, undefined, "iframe's content document");
assert_equals(iframeDoc.fullscreenElement, null, "iframe's fullscreen element");
// Because the iframe was removed, its browsing context was discarded and
// its contentDocument has become null. Because that browsing context was
// neither a descendant browsing context nor had an active document,
// nothing at all was done with it in the exit fullscreen algorithm, so
// its fullscreenElement is unchanged.
assert_equals(iframe.contentDocument, null, "iframe's content document");
assert_equals(iframeDoc.fullscreenElement, iframeDoc.body, "iframe's final fullscreen element");
});
});
});