- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Nov 2024 00:50:25 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[web-animations-2] Progress APIs`, and agreed to the following: * `RESOLVED: change Animation.progress to Animation.overallProgress` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> DavidA: we added a property field, it reflects the progress of the animation in a way that reflects the iterations of the animation<br> <TabAtkins> DavidA: there is a .progress that exists in AnimationEffect that has a .getComputedTiming() function<br> <TabAtkins> DavidA: but that only reflects the progress of the current animation<br> <TabAtkins> DavidA: got some feedback that it coudl be confusing to share the name since they mean different things<br> <TabAtkins> DavidA: wanted to consider renaming the Animation progress field either totalProgress or currentProgress<br> <TabAtkins> DavidA: not sure which is better to go with<br> <TabAtkins> DavidA: currentProgress is related to currentTime<br> <TabAtkins> DavidA: but totalProgress more strongly reflects taht it covers all the iterations<br> <TabAtkins> fantasai: okay so it's a .progress on AnimationEffect...<br> <TabAtkins> DavidA: no, on Animation itself<br> <TabAtkins> fantasai: is there one on AnimationEffect?<br> <TabAtkins> DavidA: indirectly, kinda<br> <DavidA> AnimationEffect.getComputedTiming().progress<br> <TabAtkins> vmpstr: yehonatan also said he thinks progress if fine and he'd find currentProgress confusing<br> <dholbert> https://www.w3.org/TR/web-animations-1/#calculating-the-overall-progress<br> <TabAtkins> dholbert: WebAnim 1 uses overallProgress<br> <TabAtkins> dholbert: it differentiates that from "simple" iteration progress<br> <fantasai> https://drafts.csswg.org/web-animations-1/#dictdef-computedeffecttiming<br> <TabAtkins> astearns: "overall" is just a name in the algo, not part of the exposed API?<br> <TabAtkins> dholbert: yeah<br> <fantasai> .endTie<br> <fantasai> .endTime<br> <fantasai> .activeDuration<br> <fantasai> .localTime<br> <fantasai> .progress<br> <TabAtkins> fantasai: so this is on an object called ComputedEffectTiming, which has...<br> <fantasai> .currentIteration<br> <TabAtkins> fantasai: and we're suggesting renaming .progress<br> <TabAtkins> fantasai: we currently have .activeDuration, .localTime, .currentIteration<br> <TabAtkins> DavidA: Oh, not the progress field on this object<br> <TabAtkins> DavidA: The one on the Animation class<br> <astearns> I kind of like `overallProgress`<br> <TabAtkins> yeah i'm kinda leaning toward overall<br> <fantasai> https://drafts.csswg.org/web-animations-1/#the-animation-interface<br> <TabAtkins> DavidA: .progress on ComputedEffectTiming has existed for a while, changing woudl be hard<br> <astearns> s/ComputedEffectTiming/getComputedTiming/<br> <TabAtkins> fantasai: can you string multiple Animations together?<br> <TabAtkins> DavidA: I'm not sure...<br> <TabAtkins> dholbert: i'm slightly uneasy about "total" because it sounds like a summation<br> <TabAtkins> +1<br> <fantasai> +1<br> <TabAtkins> astearns: I'd expect "total progress" to not change over time<br> <TabAtkins> DavidA: okay so overallProgress is still something we could consider, or currentProgress<br> <TabAtkins> fantasai: since timingeffect has currentTime and progress, what's the problem with just using progress on this?<br> <fantasai> s/currentTime/localTime/<br> <TabAtkins> fantasai: you'd get the context off of which object you're getting from<br> <astearns> request for something other than `progress`: https://github.com/w3ctag/design-reviews/issues/994#issuecomment-2427287323<br> <TabAtkins> astearns: [summarizes Jeffrey's comment]<br> <fantasai> TabAtkins: effect timing can run an animation multipel times, and progress gives you progress of the iteration<br> <fantasai> TabAtkins: this is a 0-1 and done thing, so it's a different concept than what the effect timing one is<br> <fantasai> TabAtkins: can't change that one, but maybe use a different word here<br> <TabAtkins> fantasai: i don't mind overall progress, i'm just saying we both have startTimes, they mean different things<br> <fantasai> fantasai: can tell from context<br> <fantasai> TabAtkins: progress has a different interpretation, because [missed]<br> <fantasai> TabAtkins: AnimationEffect has a .endTime<br> <fantasai> TabAtkins: Effect timing and animation have same interpretation of those<br> <dbaron> (last 2 lines were answering vmpstr asking about whether startTime has the same meaning on both)<br> <fantasai> TabAtkins: Animation has a .startTime and no .endTime / AnimationEffect has .endTime and no .startTime<br> <fantasai> vmpstr: Progress, one cycles per iteration, so wouldn't be the same value at any particular point<br> <fantasai> TabAtkins: for progress, right<br> <fantasai> vmpstr: but if startTime and endTime both existed on the same object, they would be the same, right?<br> <fantasai> TabAtkins: AFAICT from a quick read, they refer to the same type of concept<br> <fantasai> TabAtkins: it's beginning of whole thing it's doing, vs iteratin<br> <fantasai> astearns: gist I'm getting, is ppl think there's enough difference to have a different name<br> <TabAtkins> fantasai: i'm okay with overallProgress<br> <TabAtkins> astearns: so proposed resolution is we change Animation.progress to Animation.overallProgress<br> <TabAtkins> RESOLVED: change Animation.progress to Animation.overallProgress<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8799#issuecomment-2461097047 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 November 2024 00:50:26 UTC