Re: [csswg-drafts] [web-animations-2] Progress APIs (#8799)

The CSS Working Group just discussed `[web-animations-2] Progress APIs`, and agreed to the following:

* `RESOLVED: Add progress to Animation and make it readonly`

<details><summary>The full IRC log of that discussion</summary>
&lt;faceless> present-<br>
&lt;bramus> flackr: So WAAPI is very focused on absolute times, but with scroll-driven aninamations, developers often just work with progress instead of time<br>
&lt;bramus> flackr: seems like a reasonable thing to add, so there is a proposal to get the current progress which is a calcuation between start and and end time<br>
&lt;bramus> flackr: also need to specify what hsould happen for infinitely repeating animations<br>
&lt;bramus> flackr: Proposal is adding currentProgress to Animation<br>
&lt;bramus> flackr:  it is calculated as  currentTime / effect endTime<br>
&lt;bramus> flackr: propose to make it readonly for now<br>
&lt;bramus> s/repeating/duration/<br>
&lt;bramus> Rossen_: Any feedback?<br>
&lt;ydaniv> I proposed "progress" instead of "currentProgress"<br>
&lt;TabAtkins> +1<br>
&lt;TabAtkins> (to the current proposal, no opinion on naming)<br>
&lt;bramus> Rossen_: You are taking into account the feedback from ydaniv?<br>
&lt;bramus> flackr: Yes, he proposed currentProgress instead of progress<br>
&lt;bramus> flackr: dont object to this shorter name and computedTIming value from the effect is also called progress<br>
&lt;bramus> Rossen_: what about read/write vs readonly?<br>
&lt;bramus> flackr: then have to decide how to handle infinite duration animation<br>
&lt;bramus> Rossen_: starting with readonly gives up path to go forward later<br>
&lt;bramus> Rossen_: Should we formulate as readonly? not hearing objections from yehonathan<br>
&lt;bramus> flackr: would be happy with that<br>
&lt;bramus> bramus: me too<br>
&lt;bramus> Rossen_: objections to adding as readonly?<br>
&lt;bramus> Rossen_: Not hearing anything<br>
&lt;bramus> bramus: and the name?<br>
&lt;bramus> flackr: we said progress<br>
&lt;bramus> flackr: Proposed resolution: add progress to Animation and make it readonly<br>
&lt;bramus> RESOLVED: Add progress to Animation and make it readonly<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8799#issuecomment-1561576205 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 24 May 2023 16:46:46 UTC