Bug 1402170 - Use template strings in processing-a-keyframes-argument.html; r?hiro
But only in a couple of places where it makes the test more readable.
MozReview-Commit-ID: 6zVJ6h7Zb3k
--- a/testing/web-platform/tests/web-animations/interfaces/KeyframeEffect/processing-a-keyframes-argument.html
+++ b/testing/web-platform/tests/web-animations/interfaces/KeyframeEffect/processing-a-keyframes-argument.html
@@ -59,28 +59,28 @@ function GetTestKeyframeSequence(testPro
for (const prop of gNonAnimatableProps) {
test(function(t) {
const testKeyframe = new TestKeyframe(prop);
new KeyframeEffect(null, testKeyframe);
assert_equals(testKeyframe.propAccessCount, 0, 'Accessor not called');
- }, 'non-animatable property \'' + prop + '\' is not accessed when using'
+ }, `non-animatable property '${prop}' is not accessed when using`
+ ' a property-indexed keyframe object');
}
for (const prop of gNonAnimatableProps) {
test(function(t) {
const testKeyframes = GetTestKeyframeSequence(prop);
new KeyframeEffect(null, testKeyframes);
assert_equals(testKeyframes[0].propAccessCount, 0, 'Accessor not called');
- }, 'non-animatable property \'' + prop + '\' is not accessed when using'
+ }, `non-animatable property '${prop}' is not accessed when using`
+ ' a keyframe sequence');
}
// Test equivalent forms of property indexed and sequenced keyframe syntax
function assertEquivalentKeyframeSyntax(keyframesA, keyframesB) {
const processedKeyframesA =
new KeyframeEffect(null, keyframesA).getKeyframes();