Re: [web-animations] unclear iteration start behaviour for animation sequence

On Thu, Dec 18, 2014 at 10:14 PM, "Сергей Грехов" <sgrekhov@unipro.ru> wrote:
> Hi All,
>
> It's unclear from the current spec animation sequence behaviour with not
> null iteration start. Example:
>
>     var animation1 = new Animation(target1, [], {
>         duration: 10,
>         fill: 'forwards'
>     });
>     var animation2 = new Animation(target2, [], {
>         duration: 190
>     });
>     var animation3 = new Animation(target3, [], {
>         duration: 800
>     });
>     var animationSequence = new AnimationSequence([animation1, animation2,
> animation3], {
>         iterationStart: 0.1
>     });
>     var player = document.timeline.play(animationSequence);
>
>     player.ready.then(function() {
>         // Total duration of the sequence is 1000. Because of iteration
>         // start animation should begin from moment that corresponds
>         // time 100. animation1 is finished at this time.
>         // What should be animation1 behaviour?
>         // Should animation1 be at the end time (because of fill mode
>         // forwards)? Or should not be started yet (should start at time
>         // 900)?
>     });
>
> Specification should more clearly define this behavoiur (in terms of
> scaled active time I think)

animation1 has already been played through; it's now in the
forward-filling state, and will remain that way for the rest of the
animation.

(There's no behavioral difference between starting the animation at .1
iteration, and starting it at 0 then letting it play through .1 of an
iteration, except you'll miss some events in the former case.)

~TJ

Received on Friday, 19 December 2014 20:31:51 UTC