Re: [csswg-drafts] [scroll-animations-1] Order of pause, setTimeline (#5653)

The CSS Working Group just discussed `[scroll-animations-1] Order of pause, setTimeline`, and agreed to the following:

* `RESOLVED: Accept the proposal in https://github.com/w3c/csswg-drafts/issues/5653#issuecomment-1271689506`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> https://github.com/w3c/csswg-drafts/issues/5653#issuecomment-1271689506<br>
&lt;dael> Rossen_: There's a link to the proposal https://github.com/w3c/csswg-drafts/issues/5653#issuecomment-1271689506<br>
&lt;dael> flackr: If you're using scroll linked animations with css it's possible to switch timeline and change place date in same update. Need a weel defined order<br>
&lt;dael> flackr: chrome and gecko both set timeline first and then apply paused play state which is observable so what to define that way<br>
&lt;dael> Rossen_: Any feedback?<br>
&lt;dael> Rossen_: I see Boris from gecko seemed to have same preference<br>
&lt;bramus> s/weel/well<br>
&lt;dael> flackr: I also think it's more dev friendly because play state change feels it shoudl be related to new timeline<br>
&lt;Rossen_> q?<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Accept the proposal in https://github.com/w3c/csswg-drafts/issues/5653#issuecomment-1271689506<br>
</details>


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


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

Received on Thursday, 8 December 2022 00:08:07 UTC