- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Oct 2022 19:57:33 +0000
- To: public-css-archive@w3.org
I assumed limiting to Animations which must use an animation-timeline of type document timeline implies their currentTime can only move forward. Is that not the case? Maybe an example of a use-case which should work but won't with the limitation to document-timeline would help. Btw a use-case for paused animations that I had in mind relates to network events. To avoid the latency of loading images in starting the transition. For instance an author can start the transform/size animations to move an element to its position in the new DOM but pause the cross-fade until the new image loads (or there is a timeout). ```js let fadein = document.documentElement.animate(..., { pseudoElement: "::page-transition-incoming-image(thumbnail)", } ); let fadeout = document.documentElement.animate(..., { pseudoElement: "::page-transition-outgoing-image(thumbnail)", } ); fadein.pause(); fadeout.pause(); startOnThumbnailLoadOrTimeout(fadein, fadeout); ``` -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7785#issuecomment-1278113734 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 October 2022 19:57:35 UTC