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: Clamp progress to [0,1]`

<details><summary>The full IRC log of that discussion</summary>
&lt;fserb> github-bot take up https://github.com/w3c/csswg-drafts/issues/8799<br>
&lt;fantasai> astearns: remaining question is whether we are clamping<br>
&lt;fantasai> flackr: we decided to add a progress accessor to animations<br>
&lt;fantasai> flackr: question was what to do outside the range of the animation<br>
&lt;fantasai> flackr: before animation starts or after it ends<br>
&lt;fantasai> flackr: I believe everyone is agreed that clamping is what makes sense, so want to resolve on it<br>
&lt;fantasai> flackr: [0%, 100%]<br>
&lt;fantasai> flackr: maps to the keyframe you're showing, assuming animation is in effect<br>
&lt;fantasai> astearns: any disagreement?<br>
&lt;fantasai> RESOLVED: Clamp progress to [0,1]<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-2378058917 using your GitHub account


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

Received on Thursday, 26 September 2024 22:37:40 UTC