Re: [csswg-drafts] [web-animations-1] Don't preserve current time for scroll linked animations when changing playbackRate (#2075)

The CSS Working Group just discussed `[web-animations-1] Don't preserve current time for scroll linked animations when changing playbackRate`, and agreed to the following:

* `RESOLVED: Accept flackr's fix`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> flackr: We set up SLA so the time of th etimeline in which you play them isn't used for the start time, that would lead to skew with pages starting their SLA after the scroll started<br>
&lt;TabAtkins> flackr: We didn't account for some of the other APIs tho. I did an audit and playbackRate is the only one we haven't fixed yet.<br>
&lt;TabAtkins> flackr: So this proposal is that SLA doesn't try to preserve their current time when you change playback rate<br>
&lt;TabAtkins> flackr: I landed a simple fix, but Kevin brought up that when you reverse the naimation via negative playback rate, we shoudl fix it the same way as when you actually do a reversed animations.<br>
&lt;TabAtkins> flackr: So I landed a fix to change the start time there.<br>
&lt;TabAtkins> flackr: This aligns the playbackRate change to the behavior when you call .play()<br>
&lt;Rossen_> Zakim, open queue<br>
&lt;Zakim> ok, Rossen_, the speaker queue is open<br>
&lt;TabAtkins> I didn't look in detail but the expl makes sense to me<br>
&lt;TabAtkins> Rossen_: Objections?<br>
&lt;TabAtkins> RESOLVED: Accept flackr's fix<br>
</details>


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


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

Received on Wednesday, 21 December 2022 17:49:33 UTC