Re: [csswg-drafts] [scroll-animations] Should animation events fire every time active range is left / reentered? (#4324)

The CSS Working Group just discussed `[scroll-animations] Should animation events fire every time active range is left / reentered?`, and agreed to the following:

* `RESOLVED: Animation events fire for scroll linked animations as defined by web animations spec`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> https://github.com/w3c/csswg-drafts/issues/4324#issuecomment-1325707643<br>
&lt;fantasai> Proposal: https://github.com/w3c/csswg-drafts/issues/4324<br>
&lt;fantasai> Proposal: https://github.com/w3c/csswg-drafts/issues/4324#issuecomment-1325707643<br>
&lt;dael> flackr: An open question we had lingering about with a scroll linked animation you can repeatedly enter before or after phase by scrolling. As defined this fires animation events. Should it?<br>
&lt;dael> flackr: birtles and I chatted and we think it seems reasonable to fire events as define. Prop is events fire for scroll linked animations as specified<br>
&lt;dael> flackr: Second part we can take up separately<br>
&lt;dael> Rossen_: I see some back and forth on this. Anyone want to express other opinions?<br>
&lt;dael> Rossen_: Taking the silence as no additional opinions<br>
&lt;dael> flackr: Animation events fire for scroll linked animations as defined by web animations spec<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Animation events fire for scroll linked animations as defined by web animations spec<br>
&lt;dael> flackr: Second part, CSS animations have an animation start event. Web animations have a ready promise which is not quite the same. Ready would resolve once.<br>
&lt;dael> flackr: Would it be useful to add a start event that developers could use to trigger on same condition. Every time you go from before animation is active to when it's active<br>
&lt;Rossen_> q?<br>
&lt;dael> birtles: I think you need something if it's possible to finish and then go unfinished good for authors to detect. Don't know it's a start event b/c that would relate to the delay. Maybe just an active event. Need to define some way for authors to know it goes from finished to not finished<br>
&lt;bramus> q+<br>
&lt;dael> flackr: Sounds like something we should come up with ideas and bring back.<br>
&lt;dael> flackr: Let's stick with first resolution and move on<br>
&lt;Rossen_> ack bramus<br>
&lt;dael> bramus: Wondering how that would work with various phases. I'm okay if we come up with some ideas to discuss<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4324#issuecomment-1341786309 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:13:34 UTC