fune/testing/web-platform/tests/css/css-paint-api/two-element-custom-property-animation.https.html
Xida Chen 6914f6479f Bug 1679555 [wpt PR 26661] - Fix a few flaky test in css-paint-api/, a=testonly
Automatic update from web-platform-tests
Fix a few flaky test in css-paint-api/

The problem of these tests is that we do a takeScreenShot in the
rAF, and a rAF doesn't guarantee that the animation is ready, so
it can be easily flaky given that the animations are running on
the compositor thread.

This CL fixes it so that it calls takeScreenShot when the animation
ready promise is resolved, and the makes sure that the animation
already begun.

Bug: 1133821
Change-Id: I4fae6ccb9fe992316831d4d2013e1aa32eb52c82
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562728
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#831650}

--

wpt-commits: 130f163afe563f8d858e960570bfdd9dc02cdbae
wpt-pr: 26661
2020-12-03 09:54:50 +00:00

92 lines
2.7 KiB
HTML

<!DOCTYPE html>
<html class="reftest-wait">
<link rel="help" href="https://drafts.css-houdini.org/css-paint-api/">
<link rel="match" href="two-element-custom-property-animation-ref.html">
<style>
#footainer {
width: 200px;
height: 200px;
}
.fooanimate {
background-image: paint(foo);
/* Use long animations that start at 50% progress where the slope of the
selected timing function is zero. By setting up the animations in this way,
we accommodate lengthy delays in running the test without a potential drift
in the animated properties values. This is important for avoiding flakes,
especially on debug builds. The screenshots are taken as soon as the
animations are ready, thus the long animation duration has no bearing on
the actual duration of the test. */
animation: expand 1000000s cubic-bezier(0,1,1,0) -500000s;
}
#bartainer {
width: 200px;
height: 200px;
}
.baranimate {
background-image: paint(bar);
animation: colorChange 1000000s cubic-bezier(0,1,1,0) -500000s;
}
@keyframes expand {
0% { --foo: 0; }
100% { --foo: 200; }
}
@keyframes colorChange {
0% { --bar: rgb(200, 0, 0); }
100% { --bar: rgb(0, 200, 0); }
}
</style>
<script src="/common/reftest-wait.js"></script>
<script src="/common/worklet-reftest.js"></script>
<body>
<div id="footainer"></div>
<div id="bartainer"></div>
<script id="code" type="text/worklet">
registerPaint('foo', class {
static get inputProperties() { return ['--foo']; }
paint(ctx, geom, properties) {
let fooValue = parseFloat(properties.get('--foo').toString());
ctx.fillStyle = 'green';
ctx.fillRect(0, 0, fooValue, fooValue);
}
});
registerPaint('bar', class {
static get inputProperties() { return ['--bar']; }
paint(ctx, geom, properties) {
ctx.fillStyle = properties.get('--bar').toString();
ctx.fillRect(0, 0, 200, 200);
}
});
</script>
<script type="text/javascript">
CSS.registerProperty({
name: '--foo',
syntax: '<number>',
initialValue: '0',
inherits: false
});
CSS.registerProperty({
name: '--bar',
syntax: '<color>',
initialValue: 'rgb(0, 0, 0)',
inherits: false
});
</script>
<script>
var code = document.getElementById('code').textContent;
var blob = new Blob([code], {type: 'text/javascript'});
CSS.paintWorklet.addModule(URL.createObjectURL(blob)).then(function() {
document.getElementById('footainer').classList.add('fooanimate');
document.getElementById('bartainer').classList.add('baranimate');
const animations = document.getAnimations();
// Wait for all animations to start before completing the test.
Promise.all([animations[0].ready, animations[1].ready]).then(() => {
takeScreenshot();
});
});
</script>
</body>
</html>