W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2016

Re: [csswg-drafts] [css-transitions][css-animations] Complex timing functions

From: VisibleCode via GitHub <sysbot+gh@w3.org>
Date: Sun, 31 Jul 2016 06:32:49 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-236414158-1469946767-sysbot+gh@w3.org>
The thing with range() being optional is mostly so you keep using the 
existing syntax:

animation-timing-function: ease-in;

rather than having to explicitly write:

animation-timing-function: ease-in range(0.0, 1.0);

But it also means you can just chain a bunch of easings and get a 
continuous result, for example:

animation-timing-function: ease-in, 30% ease-in-out, 70% ease-out;

and get something equivalent to:

animation-timing-function: ease-in range(0.0, 0.3), 30% ease-in-out 
range(0.3, 0.7), 70% ease-out range(0.7, 1.0);

So it's actually not bad for hand-authoring in simple to medium cases.

GitHub Notification of comment by visiblecode
Please view or discuss this issue at 
using your GitHub account
Received on Sunday, 31 July 2016 06:32:57 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:00 UTC