author Hiroyuki Ikezoe <>
Mon, 27 Jun 2016 12:52:53 +0900
changeset 385379 0ee465a584fa495614b976884f9731d93e0e0554
permissions -rw-r--r--
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

<!DOCTYPE html>
Opacity animation does not destroy stacking context when the animation
has finished but has fill:backwards
span {
  height: 100px;
  width: 100px;
  position: fixed;
  background: green;
  top: 50px;
@keyframes Opaque {
  from, to { opacity: 1 }
#test {
  width: 100px; height: 100px;
  background: blue;
  animation: Opaque 100s 100s backwards;
<div id="test"></div>