- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Jan 2023 20:08:26 +0000
- To: public-css-archive@w3.org
Yeah, what Jake showed is what I was referring to in #7785. As I understood from that resolution is that an author can pause the animation and control it via rAF to either direction, and it should keep the pseudo tree alive while the animations are paused. So I'm a little confused why we still need #8132 to solve that. Regardless, to get the reversed transition working you need to "hold" the progress at ~0.001%, update the DOM back to previous state "manually", and then reverse all of them manually, and then the hacky bit with cancelling the "holding animation". And all of this for a rAF controlled animation. So I think there should be a more dev-friendly way to reverse all underlaying animations and/or cancel the transition in case of: - Transition's animations are driven by rAF (later may be scroll-driven or future pointer-driven?) and then author wants to essentially cancel the Transition (or reverse it back to 0% and cancel) once the user made a gesture all the way back to initial position. - Transition's animations are linked to the document timeline and the user reversed the navigation in mid-transition, e.g. clicked "backspace" And then we can still reuse current pseudo tree, and have a way of holding 0% progress, update DOM back, and then cancel and remove the pseudo tree. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7957#issuecomment-1377787554 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 January 2023 20:08:27 UTC