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: Sat, 30 Jul 2016 22:45:13 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-236393986-1469918711-sysbot+gh@w3.org>
@vidhill's proposal is pretty much the distilled essence of procedural
 animation. Using Javascript is great because you can directly specify
 any function you want. It's roughly what I'd personally want for most
 things. Main issue is the syntax; I think it'd be better if you could
 reference a Javascript function in the page context rather than 
having to use a separate .js resource.

That said, it's definitely a Houdini thing, for the reasons people 
have mentioned. One, it obviously requires Javascript to be available.
 And two, there has to be some guarantee that the animation function 
won't be poking at the DOM or network or global state. Neither is a 
problem in the context of Houdini, which assumes the availablity of JS
 to begin with, and has the "worklet" concept for isolating functions 
from the page's normal JS context. Houdini also should solve the 
"reference a fragment of JS from CSS somehow" problem in a general 

GitHub Notification of comment by visiblecode
Please view or discuss this issue at 
using your GitHub account
Received on Saturday, 30 July 2016 22:45:20 UTC

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