Currently we fail a handful of the WPT tests relating to processing a keyframes argument:
- external/wpt/web-animations/interfaces/KeyframeEffect/processing-a-keyframes-argument-001.html
FAIL A list of values returned from a custom iterator should be ignored Failed to construct 'KeyframeEffect': Lists of values not permitted in array-form list of keyframes
FAIL Only properties defined directly on keyframes are read assert_equals: properties on ComputedKeyframe #0 should match expected "composite,computedOffset,easing,offset,top" but got "composite,computedOffset,easing,height,left,offset,top"
FAIL Only properties defined directly on property-indexed keyframes are read assert_equals: properties on ComputedKeyframe #0 should match expected "composite,computedOffset,easing,offset,top" but got "composite,computedOffset,easing,left,offset,top"
FAIL Properties are read in ascending order by Unicode codepoint assert_array_equals: property access order property 3, expected "left" but got "marginLeft"
We should fix up these remaining failures in our algorithm implementation.
Comment 1 by smcgruer@chromium.org
, Mar 31 2018