- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 May 2023 16:35:08 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[scroll-animations-1][css-animations-2] Out-of-range range offsets`, and agreed to the following: * `RESOLVED: allow timeline ranges outside of 0-100% range, and use them as-is for existing animation start-time and duration calculations.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> flackr: This is about whether we allow animation-range offsets outside the 0-100% range, and if so what we do with them<br> <TabAtkins> flackr: I propose we do allow them, and we have the animation-range account for that range (so the animation conceptually begins before the timeline start). This is already well-defined.<br> <TabAtkins> flackr: Also fairly consistent with the way we allow keyframe offsets outside the animation active interval.<br> <TabAtkins> (Also consistent with gradients.)<br> <TabAtkins> flackr: I think it's also useful to have negative values so you can define an animation portion as starting before some other range.<br> <TabAtkins> +1<br> <ydaniv> q+<br> <miriam> ack ydaniv<br> <TabAtkins> ydaniv: Is there weirdness with non-named ranges, having values outside the range?<br> <TabAtkins> flackr: Why is that weird<br> <TabAtkins> ydaniv: With named ranges you may still have more scroll range<br> <TabAtkins> ydaniv: when you use the entire scroll range there's nothing outside of 0-100<br> <TabAtkins> flackr: That's not true with view timelines, because their complete range is "cover" but they do produce values outside of 0-100<br> <TabAtkins> flackr: But even so, having implicit clipping at the scroll limit is alreayd part of the API in terms of how keyframes work, and how named ranges work if you can't scroll to that full range. So I think it's consistent.<br> <TabAtkins> miriam: So if the value is outside 0-100 and there's no way to get to there, it's clipped?<br> <TabAtkins> flackr: It's implicitly clipped - if you have an animation start at -20%, when the animation actually starts it'll actually have already gone thru 20% of the animation.<br> <TabAtkins> flackr: Proposed resolution is allow timeline ranges outside of 0-100% range, and use them as-is for existing animation start-time and duration calculations.<br> <TabAtkins> miriam: Objections?<br> <TabAtkins> RESOLVED: allow timeline ranges outside of 0-100% range, and use them as-is for existing animation start-time and duration calculations.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8578#issuecomment-1551726087 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 May 2023 16:35:10 UTC