This is a tracking bug for implementing KeyframeEffectReadOnly::getKeyframes(). Most of our WPT failures are (at least initially) due to our lack of support for this method.
Doing so is quite a task, as it requires us to re-do how we treat keyframes. My current plan is to:
* Make StringKeyframe track 'uncomputed' keyframes - short-hand, possibly invalid (property, value) pairs.
* Make StringKeyframe::{CSS,SVG}PropertySpecificKeyframe track 'computed' keyframes - long-hand, only valid, and apply the short-hand deduping algorithm from the spec (https://www.w3.org/TR/web-animations-1/#computed-keyframes).
This may or may not be feasible.
Comment 1 by smcgruer@chromium.org
, Oct 24 2017