Re: [csswg-drafts] [css-scroll-animations] Rethinking declarative syntax for scroll-linked animations (#6674)

I'm working on rewriting the spec with @flackr's help in the rewrite.bs file in the repo; I'll propose replacing the existing draft once it's a bit more complete.
https://drafts.csswg.org/scroll-animations-1/rewrite

I've also opened up some follow-up issues:
* https://github.com/w3c/csswg-drafts/issues/7059 for transition delays, see https://github.com/w3c/csswg-drafts/issues/6674#issuecomment-945845884
* https://github.com/w3c/csswg-drafts/issues/7047 for scope of timeline names, @ogerchikov it'd be helpful if you could post some concrete examples into that issue so we can make sure use cases get covered
* https://github.com/w3c/csswg-drafts/issues/7044 for entry/exit animations. @bramus, would you mind copying https://github.com/w3c/csswg-drafts/issues/6674#issuecomment-930542414 into that issue?
* https://github.com/w3c/csswg-drafts/issues/7045 about whether to represent API time values (currentTime/startTime/endTime/duration etc.) as pixels or percents here
* https://github.com/w3c/csswg-drafts/issues/7046 about whether we want scroll() to accept a container-name, or if we prefer having the scroll-timeline-* properties

Please redirect your specific comments there, I'll keep this one open for switching up the overall direction and close it out once we're ready to fold in all the edits. :) Thanks!!

-- 
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6674#issuecomment-1040906711 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 February 2022 23:35:31 UTC