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

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

From: Rachel Nabors via GitHub <sysbot+gh@w3.org>
Date: Tue, 19 Jul 2016 01:06:58 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-233503509-1468890417-sysbot+gh@w3.org>
Interesting perspective, @vidhill. Thanks for sharing. I am personally
 a bit hesitant to wait to see how Houdini's adoption goes and what 
hiccups will come down the line when we could nail down a spec today. 
But if we can't, you very well may have described the future.

@grorg Thanks for joining the conversation! I'd love to see browsers 
offer more defaults than just `ease-in`, `linear`, etc. I was thinking
 adding [`easeOutQuint`](http://easings.net/#easeOutQuint) and the 
like. That's probably for another discussion, though, as we're 
chatting more about how to make a robust timing function that could 
underly other timing functions (like `spring()` and `steps()` ) and 
possibly be an export format for programs like After Effects. I've 
seen a real need from designers, as I know you have. What do you 

GitHub Notification of comment by rachelnabors
Please view or discuss this issue at 
using your GitHub account
Received on Tuesday, 19 July 2016 01:07:06 UTC

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