| Index: third_party/WebKit/LayoutTests/imported/wpt/web-animations/animation-model/keyframe-effects/the-effect-value-of-a-keyframe-effect-expected.txt
|
| diff --git a/third_party/WebKit/LayoutTests/imported/wpt/web-animations/animation-model/keyframe-effects/the-effect-value-of-a-keyframe-effect-expected.txt b/third_party/WebKit/LayoutTests/imported/wpt/web-animations/animation-model/keyframe-effects/the-effect-value-of-a-keyframe-effect-expected.txt
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..919f7a2e84d19e7f105b7d4790b414e62b4f3759
|
| --- /dev/null
|
| +++ b/third_party/WebKit/LayoutTests/imported/wpt/web-animations/animation-model/keyframe-effects/the-effect-value-of-a-keyframe-effect-expected.txt
|
| @@ -0,0 +1,7 @@
|
| +This is a testharness.js-based test.
|
| +FAIL Overlapping keyframes at 0 and 1 use the appropriate value when the progress is outside the range [0, 1] assert_equals: When progress is negative, the first keyframe with a 0 offset should be used expected "0" but got "0.151456"
|
| +PASS Overlapping keyframes between 0 and 1 use the appropriate value on each side of the overlap point
|
| +FAIL Test visibility clamping behavior. assert_equals: Visibility when progress = 0. expected "hidden" but got "visible"
|
| +FAIL Test visibility clamping behavior with an easing that has a negative component assert_equals: Visibility when progress = 0. expected "hidden" but got "visible"
|
| +Harness: the test ran to completion.
|
| +
|
|
|