You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[web-animations-1] null or undefined keyframe in iterable keyframe object causes an assertion failure #14113
If Type(nextItem) is not Undefined, Null or Object, then throw a TypeError and abort these steps.
Append to processed keyframes the result of running the procedure to process a keyframe-like object passing nextItem as the keyframe input with the allow lists flag set to false.
But process a keyframe-like object explicitly only takes an object, not null or undefined. And indeed it eventually calls EnumerableOwnNames on its input argument (Step 3), which fails an assertion when the input is not an object.
Activity
birtles commentedon Sep 11, 2026
Seems like a clear editorial issue since there are WPT for this that all engines pass: https://github.com/web-platform-tests/wpt/blob/e0551eab00f7a5164207ad664e4f98cd7c20bba3/web-animations/interfaces/KeyframeEffect/processing-a-keyframes-argument-001.html#L382-L410
[web-animations-1] Fix 'process a keyframe-like argument' to handle n…