gecko-dev/layout/reftests/css-animations/stacking-context-transform-none-with-fill-forwards.html
Hiroyuki Ikezoe d6944d301d Bug 1278136 - Part 2: We should not check whether the animation can run on the compositor or it's paused when determining if we should create a stacking context. r=birtles,mattwoodrow
We should create a stacking context for any transform or opacity animations
that are either "in effect" (what we currently do) OR "current", i.e.
scheduled to run or running. *BUT* for now, we don't create any stacking
context in before phase without fill:backwards or fill:both because the
property never wins in cascade until the animation gets "in effect".  This
restriction will be removed in a subsequent patch in this bug after landing
bug 1279403.

MozReview-Commit-ID: 8RyLJNPtoKI

--HG--
rename : layout/reftests/css-animations/stacking-context-transform-animation-ref.html => layout/reftests/css-animations/stacking-context-animation-ref.html
extra : rebase_source : 0d9c8d9e03ca0d400e9b376b9416fbabffd10034
2016-06-27 12:52:53 +09:00

25 lines
450 B
HTML

<!DOCTYPE html>
<title>
Transform animation does not destroy stacking context when the animation
has finished but has fill:forwards
</title>
<style>
span {
height: 100px;
width: 100px;
position: fixed;
background: green;
top: 50px;
}
@keyframes TransformNone {
from, to { transform: none }
}
#test {
width: 100px; height: 100px;
background: blue;
animation: TransformNone 0s forwards;
}
</style>
<span></span>
<div id="test"></div>