- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Dec 2022 00:56:01 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[scroll-animations-1] What's the point of animation-range?`, and agreed to the following: * `RESOLVED: Animation range and animation delay are separate things that compound` <details><summary>The full IRC log of that discussion</summary> <Rossen_> https://github.com/w3c/csswg-drafts/issues/7901#issuecomment-1325538928<br> <dael> fantasai: When we were trying to figure out how to attach an animation to different ranges, named ranges in the timeline. Entry phase, exit phase, and the like and want to attach to some<br> <dael> fantasai: We allowed keyframes to take a named range as well a % to reprsent progress intot he range to be able to built animation that crosses ranges.<br> <dael> fantasai: Also wanted to take existing keyframes and attach to a range<br> <dael> fantasai: Did that with animation delay as a way of indicating where we wanted to attach it. Could give a named range and % into the range as delay<br> <dael> fantasai: That has weird ergonomix for author. Want to attach to entry phase and set animation delay to entry. Reason why we have animation range property is to make it feel less odd<br> <dael> fantasai: Becomes a question if we think about interaction what makes the most sense. flackr comment has several ways to make them intersect or have different responsibilities<br> <dael> flackr: I can present 1 & 2. Option 1 is keeping things close to today. Animation delay only spec start delay. Prop is turnt hat into a shorthand for start and end delay. preserve single value for compat<br> <dael> flackr: It was accept timeline range in each. animation range is for the case you want to cover a complete range. animation-range: enter sets it to enter 100%<br> <bramus> s/sets it to enter 100%/sets it to enter 0% enter 100%<br> <birtles> q+<br> <dael> flackr: Option 2 is closer to preserve existing delay as is and introduce animation range where you can spec a range, range start, range end and it maps to internal values. Effectively makes animation-delay somewhat of a legacy property b/c only specs start and range is everything delay does<br> <Rossen_> q?<br> <dael> fantasai: Third option is animation delay and animation range take effect at same time. Range set the range and delay is an inset into that itme<br> <dael> fantasai: animation-range:entry and animation-delay:value I start that value into the range.<br> <dael> fantasai: I think that has an advantage that it keeps delay simple and reasonable interaction between delay and range.<br> <dael> fantasai: I think those are the proposals on the issue<br> <dael> fantasai: My preference is 3rd<br> <dael> flackr: I prefer 3rd as well<br> <dael> birtles: I think we should think about why introduced group effects. Animation delay is relative to parent effect where if you have a sequence and delay b it'll offset start relative to a. Then what would an absolute delay mean? Or a range? We should think about that<br> <dael> birtles: Maybe we would decide they should be separate and delay is effect and range is animation as a whole<br> <bramus> q+<br> <Rossen_> ack b<br> <Rossen_> ack b<br> <dael> bramus: To make sure I understad, prop is to set an animation range to entry and then set an animation delay to 25% 75%. Is that correct?<br> <dael> birtles: That sounds like what it would be. Animation range applies first and puts on timeline<br> <Rossen_> ack fantasai<br> <dael> flackr: Slight correction. you probably didn't mean 75% end delay. Animation-delay:end is same meaning where it's amount of time after effect. 25% 25% would do wha tyou expect<br> <bramus> Got it<br> <dael> fantasai: Suppose in future have named, time based ranges. And you say you want to animation this during window. Express the delay in ms and you can do start and end and ms cut into it. If we add length-based you could also cut in with a length<br> <dael> fantasai: I think we still want to allow range to be entry 10% or whatever so you would add up %. If doing time + % it points to the point you've described. You add additional padding with the delay<br> <dael> Rossen_: I'm trying to make sense of the silence. Looks like "okay" silence<br> <dael> flackr: I think option 3 sounds good and might be better for previous issue<br> <dael> Rossen_: Prop?<br> <dael> fantasai: Animation range and animation delay are separate things that compound<br> <dael> Rossen_: Additional opinions or objections?<br> <dael> RESOLVED: Animation range and animation delay are separate things that compound<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7901#issuecomment-1341819680 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:56:03 UTC