W3C home > Mailing lists > Public > www-style@w3.org > August 2014

Re: [css-animations] When/how are keyframe values computed?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sun, 10 Aug 2014 21:55:40 -0700
Message-ID: <CAAWBYDC3toLX9qWyLa=APN9qfsfi8QesH36KyF_toJ7jPLAA2A@mail.gmail.com>
To: Lea Verou <lea@verou.me>
Cc: Sylvain Galineau <galineau@adobe.com>, "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
On Sun, Aug 10, 2014 at 8:50 PM, Lea Verou <lea@verou.me> wrote:
> On Aug 11, 2014, at 04:31, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> Minus the "50% switch" behavior
> Speaking of which, I’m not sure this was a good idea:
> a) How are we going to explain animation-timing-function which switches immediately? What about transition and its longhands? It seems more consistent to say the switch occurs immediately, unless changed by a timing-function (how would that work? In any case, authors need to be able to tweak *when* the switch happens, *especially* with transitions, otherwise this change will bring more harm than good).

I don't know what you mean by this.  The "50%" is 50% progress through
the timing function.  You can tweak that to your heart's content, and
make the switch happen anywhere from the beginning to the end.

> b) If the switch occurs immediately, this has no effect in transitions unless a timing-function was used to change it, which minimizes the backwards compat issues we’re discussing even more.

A timing function always applies.

Received on Monday, 11 August 2014 04:56:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:24 UTC