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

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

From: Rachel Nabors via GitHub <sysbot+gh@w3.org>
Date: Fri, 24 Jun 2016 04:21:20 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-162073359-1466742079-sysbot+gh@w3.org>
rachelnabors has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-transitions][css-animations] Complex timing functions ==
In light of the Webkit team's implementation of `spring()`, it's 
apparent we need to attend to [the issue of complex timing 
functions](https://lists.w3.org/Archives/Public/public-fx/2015JulSep/0038.html)
 sooner rather than later.

# The problem
Designers often need more advanced timing functions than can be 
described with cubic-beziers. They are not limited to spring 
functions, either. A common problem is there is no effective way to 
export a timing graph from Adobe After Effects to a timing function 
that could be used with CSS or with the Web Animations API. Currently 
designers have to hack together individual timing functions using CSS 
animation keyframes, which is impossible to do by hand in all but the 
most trifling instances.

`spring()` is just a bandaid.

# The solution
We need a format to write functions like `spring()` in, one that we 
can export to from software like AfterEffects and prototyping tools 
that have yet to be built.

I am not in a position to propose the technical specifications of this
 solution. But there are people who have that knowledge. I have 
invited them (@visiblecode) to share their proposals below.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/229 using your GitHub 
account
Received on Friday, 24 June 2016 04:21:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:20 UTC