Files
tubestation/layout/reftests/web-animations/stacking-context-transform-none-animation-before-appending-element.html
Hiroyuki Ikezoe cf4c47962a Bug 1439803 - Add reftest-no-flush flag to stacking-context-transform-none-animation-before-appending-element.html. r=birtles
If reftest-no-flush is not specified, reftest harness flushes layout in a
callback of setTimeout() that happens after paint process happened in the next
refresh driver's tick.  Thus, the paint process triggered by the layout flush
causes no invalidation changes, so reftest harness ends up waiting for the
animation end until the animation finishes.

MozReview-Commit-ID: GXvmyXh0kfV
2018-02-23 07:22:10 +09:00

32 lines
937 B
HTML

<!DOCTYPE html>
<html class="reftest-wait reftest-no-flush">
<!--
reftest-no-flush above is necessary to make invalidation changes happen.
Without it, reftest harness takes the snapshot on the next frame after the
frame that a paint for appending the element happened.
-->
<title>Transform animation whose target is not initially associated with any document creates a stacking context even if it has only 'transform:none' in its keyframe</title>
<style>
span {
height: 100px;
width: 100px;
position: fixed;
background: green;
top: 50px;
}
div {
width: 100px; height: 100px;
background: blue;
}
</style>
<span></span>
<script>
var div = document.createElement("div")
var anim = div.animate({ transform: ['none', 'none'] },
{ duration: 100000 });
anim.ready.then(() => {
document.body.appendChild(div);
document.documentElement.classList.remove("reftest-wait");
});
</script>