- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Apr 2023 15:08:40 +0000
- To: public-css-archive@w3.org
If you have to pass in the specific animation rangeStart and rangeEnd and you want the animation progress, I feel like the computed timing on the effect is a better fit, e.g.: ``` const value = animation.effect.getComputedTiming().progress; ``` I also have concerns with getCurrent**Time** being expected to produce a progress. Maybe we could consider whether we should expose progress on the animation object directly? e.g. `animation.progress` -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8669#issuecomment-1499227225 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 April 2023 15:08:41 UTC