-
Notifications
You must be signed in to change notification settings - Fork 72
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
Scroll-driven Animations #347
Comments
Also here is the explainer for this feature which goes in more details on usecases and API choices: https://github.com/w3c/csswg-drafts/blob/master/scroll-animations-1/EXPLAINER.md |
I'm not a Mozilla employee so these are just my thoughts as the current 'DOM: Animation' module owner and one of the editors of this spec (where my current involvement is focused on reviewing those parts that interact with Web Animations). I think this should be "worth prototyping" for the following reasons:
References for posterity: |
The spec has undergone a fairly radical change with greatly improved css ergonomics with working group resolutions for all of the major decision points. We are down to a very small set of issues remaining being tracked by https://github.com/w3c/csswg-drafts/projects/33. It also looks like there is also an implementation started in https://bugzilla.mozilla.org/show_bug.cgi?id=1676780. Could we get a position? |
Positive position from me, per Brian's comment, and we have been working on its CSS part already. |
FWIW, the spec. got renamed to "Scroll-driven Animations". So, when adding it to the dashboard, the entry should use the same terminology. And, I guess since there's already work for this happening, this can be labelled with "position: positive" and "ready to add". Sebastian |
Adjusting labels based on the comments above. |
* Add Scroll-driven animations (positive) Closes #347 * Apply suggestions from code review
Request for Mozilla Position on an Emerging Web Specification
Other information
There appears to be some support for this feature already (given the prior work done on it), but it would good to add an entry for it. Also the spec now contains a declarative API (@scroll-timline etc), which needs evaluation.
(cc @majido, so he knows this exists).
The text was updated successfully, but these errors were encountered: