- From: David Bokan via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Feb 2024 14:48:37 +0000
- To: public-css-archive@w3.org
> What about vtObject.finish()? I choose finish() here because the vt would first play (forwards) and reach the finished state. Yeah, if we had some manual control on the vtObject that might make sense. I was considering the case where we just make it manual by default (in the case of a non-monotonic timeline). In that scenario, calling `animation.finish` wouldn't work since the VT no longer ends when the animations are finished; you'd have to use `animation.cancel`. But I suppose we could also add a `vtObject.finish` for that case as well... > Along with vtObject.finish(), it would be nice here if there also were something like vtObject.revert() to have the animations play back to the start and then have the VT undo the DOM update. The hard part is undoing the DOM update - I don't think it's feasible to undo the update automatically; the author would have to pass in an "undo" callback. If this is common enough though it might be a nice ergonomic improvement (the author can already do all this themselves today) -- GitHub Notification of comment by bokand Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9901#issuecomment-1927171193 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 February 2024 14:48:40 UTC