Re: [csswg-drafts] [scroll-animations-1] animation-range vs animation-duration (#8405)

The CSS Working Group just discussed `[scroll-animations-1] animation-range vs animation-duration`, and agreed to the following:

* `RESOLVED: Accept proposal in the issue`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> flackr: when you specify all of animation-range-start/end/duration<br>
&lt;emilio> ... it's not possible to satisfy all of these constraints<br>
&lt;fantasai> Proposal -> https://github.com/w3c/csswg-drafts/issues/8405#issuecomment-1464810166<br>
&lt;emilio> flackr: where we've arrived is that animation-range is setting the absolute points at which an animation starts and ends and all other constraints are applied inside that range<br>
&lt;emilio> ... so your duration could make the animation shorter but a longer one would be clipped to that range<br>
&lt;emilio> ... this is my mental model as well<br>
&lt;emilio> fantasai: [goes over comment]<br>
&lt;flackr> q+<br>
&lt;Rossen_> ack fantasai<br>
&lt;Rossen_> ack flackr<br>
&lt;emilio> flackr: one point of clarification: for time-based timelines you need the range to start at the point you tell them to play<br>
&lt;emilio> fantasai: if you set a negative delay you might end up with a start before the document timeline start<br>
&lt;emilio> ... if you have an animation range that could be negative range, but you're not going to see that animation<br>
&lt;emilio> flackr: if you specified animation-range-start: 0s that implies the time at which the document loaded<br>
&lt;emilio> ... so the auto start range would be the point at which you play the animation<br>
&lt;emilio> fantasai: I see, so when we add times to animation-range it makes the model consistent<br>
&lt;emilio> YehonatanDaniv: so if duration is shorter than start-end which one takes precedence?<br>
&lt;emilio> fantasai: so if it's smaller it might clip the animation, but if the duration is larger the animation ends until the end of the range<br>
&lt;emilio> YehonatanDaniv: but if I force iterations to 1...<br>
&lt;emilio> fantasai: if you have no delay, you layout the keyframes along the duration, but if the end of the range is before, any frames after get ignored<br>
&lt;emilio> YehonatanDaniv: ok<br>
&lt;emilio> YehonatanDaniv: so start/end either define my duration if auto or a clipping range<br>
&lt;emilio> fantasai: yeah<br>
&lt;emilio> PROPOSAL: [fantasai's comment ;)]<br>
&lt;emilio> RESOLVED: Accept proposal in the issue<br>
</details>


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


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

Received on Monday, 20 March 2023 14:52:00 UTC