Skip to content

Add bounded CSS animation directions - #660

Merged
wieslawsoltes merged 1 commit into
mainfrom
feature/css-animation-direction-659
Sep 19, 2026
Merged

wieslawsoltes merged 1 commit into
mainfrom
feature/css-animation-direction-659

Conversation

@wieslawsoltes

Copy link
Copy Markdown
Collaborator

Problem

WebScene exposed animation-direction in CSS metadata but discarded it during parsing and sampling, so supported keyframes always ran forward.

Result

  • Parses and retains longhand/CSSOM and the first-animation shorthand values normal, reverse, alternate, and alternate-reverse.
  • Adds a bounded direction enum to animation configuration and signatures.
  • Maps cycle parity/progress before opacity, rotation, and filter sampling.
  • Handles negative delays, infinite cycles, exact iteration edges, finite integer/fractional terminal points, and direction-correct existing forwards/both fill.
  • Preserves exact filter-none stops, reduced motion, visibility, detach, frame-demand, lifecycle, and one-animation bounds.
  • Adds deterministic native cases, a bounded WPT-aligned browser contract/profile, capability metadata, and validation documentation.
  • Adds no ABI or AppScene change.

Play-state, backwards fill, multiple animations, WAAPI, and additional animated properties remain deferred under #242.

Closes #659.

Validation

git diff --check passed. Under the agreed fast merge policy, no local builds or runtime tests were run.

@wieslawsoltes
wieslawsoltes merged commit 8447e25 into main Sep 19, 2026
2 of 7 checks passed
@wieslawsoltes
wieslawsoltes deleted the feature/css-animation-direction-659 branch September 19, 2026 13:28
This was referenced Sep 19, 2026
This was referenced Sep 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Honor CSS animation-direction for supported keyframes

1 participant