Re: [transitions] unfinished transitions v. elapsedTime

On Mon, Sep 28, 2015 at 6:56 AM Estelle Weyl <estelle@weyl.org> wrote:

> I am taking a look at transition-delay, transition-duration and
> elapsedTime.
>
> The mozilla and blink implementations are very different.
>
> In the reverse direction in chrome the delay and duration are the full
> length of time, even if the transition in the normal direction did not
> finish. In Firefox, the delay is the full delay, but the transition
> duration is the same time that it spent going in the normal direction, not
> the full transition-duration time set. It seems like the FF implementation
> is correct.
>
>
Chrome hasn't implemented shortened reverse paths for interrupted
 transitions yet, which would explain why you're still seeing the older
behavior there.

Cheers,
     -Shane