blob: 0b825dc7c77dd7eae05ad63c263ad4876eaecb16 [file] [log] [blame]
FAIL For an input progress of 0.0, the output of a frames timing function is the first frame assert_equals: expected "0px" but got "auto"
FAIL At a frame boundary, the output of a frames timing function is the next frame assert_equals: expected "0px" but got "auto"
FAIL For an input progress of 1.0, the output of a frames timing function is the final frame assert_equals: expected "100px" but got "auto"
FAIL The number of frames is correctly reflected in the frames timing function output assert_equals: expected "0px" but got "auto"
FAIL The number of frames is correctly reflected in the frames timing function output on CSS Transitions assert_equals: expected "0px" but got "100px"
FAIL frames easing with input progress greater than 1 undefined is not a function (near '...target.animate...')
FAIL frames easing with input progress greater than 1.5 undefined is not a function (near '...target.animate...')
FAIL frames easing with input progress less than 0 undefined is not a function (near '...target.animate...')