- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Feb 2023 17:45:36 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[scroll-animations-1] Interaction with 'animation-iteration-count'`, and agreed to the following: * `RESOLVED: divide the active interval by the iteration count to get the intrinsic iteration duration` * `RESOLVED: assume an interaction count of 1, attach all the frames. that creates something that you scale down when you apply the iteraction count.` <details><summary>The full IRC log of that discussion</summary> <argyle> astearns: who takes this one?<br> <argyle> kevin ellis: could outline what's in chrome see if that makes sense<br> <argyle> kevin ellis: for scroll linked, the duration is 100% so we can workk backwards form auto. starting from 100%, remove start and end delay, take that result divided by iteration count, to get the itnrinsic iteration duration<br> <argyle> kevin ellis: this is consistent with time values rather than percentages, working out the effect end time is, then normalizing to match that to 100%<br> <argyle> kevin ellis: this makes it easy to switch from scroll linked and time based animations<br> <argyle> kevin ellis: int he case of time based, you're working forward to calc the effect end, for scrollbased you're working backwards from end target 100% to the iteration duration needs to be for everything to line up<br> <argyle> flackr: this is also paving the way for the web animations 2 proposals for sequence effect to and group effect for those to infer their duration<br> <argyle> astearns: any questions about blink's current implementation?<br> <argyle> astearns: this address your issue fantasai ?<br> <argyle> fantasai: i think so yeah<br> <argyle> flackr: we also have to decide wwhat to do about keyframes that have defined they're at a particular point of the timeline<br> <argyle> fantasai: yeah, other half of the issue<br> <argyle> flackr: my proposal was that we work out their relative proportions and then those proportions repeat. they'll no longer line up with what they declared, b ut many cases this will lmatch author intent<br> <argyle> flackr: if you have 2 iterations during enter, it'll repeat that 2 times during the entry phase<br> <argyle> fantasai: you assume an interaction count of 1, attach all the frames. that creates something that you scale down when you apply the iteraction count.<br> <argyle> fantasai: ok<br> <argyle> flackr: ok<br> <argyle> fantasai: i liek that, it kinda makes sense<br> <argyle> astearns: alright, i think this is beyond my ability to summarize<br> <argyle> astearns: what is the proposed resolution?<br> <argyle> fantasai: we have 2 right?<br> <argyle> fantasai: first, we do apply iteraction count and we divide the duration by the iteration count<br> <fantasai> -> https://github.com/w3c/csswg-drafts/issues/8233#issuecomment-1375890456<br> <argyle> kevin ellis: dividing the active interval by the iteraction count to get the intrinsic iteration duration<br> <argyle> astearns: that's the first resolution?<br> <argyle> astearns: any objections?<br> <argyle> astearns: leave it up to editors to spec terms of theyre just ways to express the resolution<br> <argyle> astearns: resolved on that<br> <fantasai> -> https://www.w3.org/TR/web-animations-1/#the-active-interval<br> <argyle> RESOLVED: divide the active interval by the iteration count to get the intrinsic iteration duration<br> <argyle> astearns: what else?<br> <argyle> flackr: 2nd was, we resolve the named keyframe offsets against the active interval and they will be repeated in these subsequent iterations<br> <argyle> RESOLVED: assume an interaction count of 1, attach all the frames. that creates something that you scale down when you apply the iteraction count.<br> <argyle> astearns: anything else on this?<br> <argyle> astearns: i imagine as you specify this out, there will be a few little details that can be editor discression or we can resolve later<br> <argyle> astearns: next 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/8233#issuecomment-1412466786 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 February 2023 17:45:38 UTC