Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[web-animations-2] [scroll-animations] Web Animations Level 2 is labeled as "Not Ready For Implementation" and yet is required to implement Scroll-driven Animations #11466

Open
graouts opened this issue Jan 9, 2025 · 3 comments

Comments

@graouts
Copy link
Contributor

graouts commented Jan 9, 2025

I've been working on implementing Scroll-driven Animations in WebKit and am concerned about the state of the relevant specs as we're getting closer to determining whether to enable this feature in an upcoming Safari release. My biggest overall concern is that the Web Animations Level 2 specification contains several incremental updates over Web Animations Level 1 which are requirements for the implementation of Scroll-driven Animations, and yet Web Animations Level 2 has a prominent "Not Ready For Implementation" label.

I think this is due to Web Animations Level 2 being the only spec where advancements over Web Animations Level 1 live, which includes both incremental updates over Level 1 for many existing procedures as well as substantial new features such as the Grouping and Synchronization features.

I believe those new features are the parts that warrant the "Not Ready For Implementation" label. To my knowledge, there are no active efforts to implement those, whereas the incremental updates have been implemented and shipped by Chrome to support Scroll-driven Animations and are being actively implemented by the WebKit and Firefox teams.

I'm not sure what the best way forward is, but I think it is important for updates to Web Animations Level 1 required for the implementation of Scroll-driven Animations to be contained in a spec that has no "Not Ready For Implementation" label. Perhaps there should be a Web Animations Level 3 spec for the new features, leaving Web Animations Level 2 as a group of incremental updates to support Scroll-driven Animations? Or perhaps those incremental updates should be made in Web Animations Level 1 since that spec is still a Working Draft?

I'm sure there are other options I don't envision and these should be discussed quickly if we want to broaden the number of implementations for Scroll-driven Animations.

@graouts
Copy link
Contributor Author

graouts commented Jan 9, 2025

Cc @flackr, @kevers-google, @andruud and @bramus.

@bramus
Copy link
Contributor

bramus commented Jan 9, 2025

I think it is important for updates to Web Animations Level 1 required for the implementation of Scroll-driven Animations to be contained in a spec that has no "Not Ready For Implementation" label.

+1 on this concern.

For completeness: there are also two appendices in the scroll-animations-1 spec that are marked for relocation to the CSS-ANIMATIONS-2 and/or WEB-ANIMATIONS-2 specs.

@birtles
Copy link
Contributor

birtles commented Jan 10, 2025

Slightly tangential, but I really want to get level 1 to CR in the coming months. To that end, I'm employing an engineer part time to work on the issues blocking that, the biggest being #5394. I really hope WebKit and Chrome are able to implement that change once it's specced.

Once the major issues in level 1 are settled, we can move stop level 2 from being a delta spec.

For now, though, would marking level 2 as ready for implementation and annotating the group and custom effect features as "not ready for implementation" work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants