W3C home > Mailing lists > Public > public-fx@w3.org > October to December 2014

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

From: Сергей Грехов <sgrekhov@unipro.ru>
Date: Fri, 19 Dec 2014 12:14:57 +0600
Message-ID: <2e0ca8ad9f748b0dbb1b41a8bcccb18a.squirrel@unipro.ru>
To: public-fx@w3.org
Cc: dom@unipro.ru
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)

--
Sergey G. Grekhov
Received on Friday, 19 December 2014 06:19:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:52 UTC