Skip to content

[web-animations-1] null or undefined keyframe in iterable keyframe object causes an assertion failure #14113

Closed

Description

@simonwuelker

Steps 5.3.6 and 5.3.7 of process a keyframes argument state:

  1. If Type(nextItem) is not Undefined, Null or Object, then throw a TypeError and abort these steps.
  2. 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

  1. birtles commented on Sep 11, 2026

    @birtles
    Contributor
  2. added a commit that references this issue on Sep 11, 2026
    86dfbf6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions