<!DOCTYPE html>
<html class="reftest-wait">
<link rel="help" href="https://drafts.csswg.org/css-backgrounds-3/#background-color">
<link rel="match" href="background-color-animation-ref.html">
<style>
.container {
width: 100px;
height: 100px;
background-color: green;
/* Use a long animation that start at 5% progress where the slope of the
selected timing function is zero. By setting up the animation in this way,
we accommodate lengthy delays in running the test without a potential drift
in the animated property value. This is important for avoiding flakes,
especially on debug builds. The screenshots are taken as soon as the
animation is ready, thus the long animation duration has no bearing on
the actual duration of the test. */
animation: bgcolor 1000000s cubic-bezier(0,1,1,0) -50000s;
}
@keyframes bgcolor {
0% { background-color: rgb(0, 200, 0); }
10% {
background-color: rgb(200, 0, 0);
animation-timing-function: cubic-bezier(0,1,1,0);
}
100% {
background-color: rgb(0, 0, 200);
animation-timing-function: cubic-bezier(0,1,1,0);
}
}
</style>
<script src="/common/reftest-wait.js"></script>
<body>
<div class="container"></div>
<script>
// This test and the "one-element-three-keyframes-animation2.html" ensure that
// we select the correct start and end keyframes for interpolation. In this
// test, the start delay of the animation makes it jump to 5% right away, and in
// the "one-element-three-keyframes-animation2.html" the start delay makes it
// jump to 50%. So for this test, we would choose the keyframes at 0% and 10%
// for interpolation, where for the other test it would be 10% and 100%.
document.getAnimations()[0].ready.then(() => {
takeScreenshot();
});
</script>
</body>
</html>
Codebase Browser
chromium