summaryrefslogtreecommitdiffstats
path: root/layout/reftests/css-animations/no-stacking-context-transform-removing-animation-in-delay.html
blob: 19605a93c1275ab2ad4bbc2dec0b89e8bb1b75f8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
<!DOCTYPE html>
<html class="reftest-wait">
<title>
Removing CSS animation in delay phase destroys stacking context
</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;
  transform: none ! important;
}
</style>
<span></span>
<div id="test"></div>
<script>
window.addEventListener("load", () => {
  var target = document.getElementById("test");
  target.style.animation = "TransformNone 100s 100s";

  // We need to wait for MozAfterPaint instead of requestAnimationFrame to
  // ensure the stacking context has been updated on the compositor.
  window.addEventListener("MozAfterPaint", function firstPaint() {
    window.removeEventListener("MozAfterPaint", firstPaint, false);
    // Here we have CSS animation on transform:none style element, so
    // there should be a stacking context.

    target.style.animation = "";
    // This time we don't need to wait for MozAfterPaint because reftest tool
    // will be received MozAferPaint event.
    requestAnimationFrame(() => {
      // Now we have only transform:none style, so we should not create any
      // stacking context.
      document.documentElement.classList.remove("reftest-wait");
    });
  }, false);
});
</script>