- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Jan 2020 22:52:50 +0000
- To: public-css-archive@w3.org
> > I want to avoid returning any epsilon values. That still leaves open the question of what is the current time of a timeline when it is in the new BeforeStart or AfterEnd states. > > My intuition here is simply that it should be 0 or effective time range respectively. That can lead to bugs if script fails to check the timeline state, but given that it is the current time that will be used by those animations that are deemed to be active in those states, I think it's the most correct behavior. > > Another option to consider is returning unresolved current time. Having BeforeStart and AfterEnd states lets the implementation apply desired animation fill mode. This seems a bit magical to me. I was thinking something more along the lines of having animations pass _both_ a "current time" and a "phase flag" (or something) to their effect, which incorporates that in the calculation of their [active time](https://drafts.csswg.org/web-animations-1/#active-time). It's a little similar to the [before flag](https://drafts.csswg.org/web-animations-1/#calculating-the-transformed-progress) we use when dealing with step functions where the step is at the start of the interval. Perhaps there's even some way to combine the two concepts? -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2066#issuecomment-577424074 using your GitHub account
Received on Wednesday, 22 January 2020 22:52:52 UTC