Re: [w3ctag/design-reviews] Spec review for Animation.progress (Issue #994)

I've updated the [explainer](https://github.com/DavMila/explainer-animation.progress) to address some of the concerns raised by  @jyasskin .
>1. It doesn't say why the developer is writing code like this in the first place.
>2. It doesn't show how updateInfo would get called. A big reason to do animations with CSS is to get them off the main thread, but this seems to require interrupting the main thread periodically to change the text.

The interest in a progress accessor was mainly driven by scroll-driven animations but it does seem to be a concept that would be valid for time-driven animations as well so I've set up a demo showing a more useful scenario: where a dev might want to synchronize audio based on the progress of an animation .

I've also:
- included a scroll-driven demo where the [currentTime](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/currentTime) of a video is set based on the progress of a scroll-driven animation.
- included a code example of how `scrollTop` could instead be used to make the before/after contrast clearer.

About the name of the property, I agree that it could be confusing, maybe a name like `totalProgress` would work better - I'll  file an issue with the CSS working group for this.

Further feedback appreciated :)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/994#issuecomment-2438605247
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/994/2438605247@github.com>