Commit Graph

2 Commits

Author SHA1 Message Date
Hiroyuki Ikezoe
72ab9ce7e5 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
2016-06-27 12:52:53 +09:00
Hiroyuki Ikezoe
1e78a617d7 Bug 1273042 - Part 3: Reftest for checking transform:none animations create a stacking context. r=birtles
This patch has two test cases one if for CSS animations and one is for web animations.

For CSS animations test cases:
@keyframes {
  from, to { transform: none; }
}

For web animtions test cases, the target element is appended after animate().

MozReview-Commit-ID: Gy1sY41jV7G
2016-06-01 16:24:34 +09:00