- From: Dean Jackson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Aug 2016 23:26:13 +0000
- To: public-css-archive@w3.org
I'm jumping in late, but I'd like to point out that script-based timing functions should be limited to script-based animations (e.g. Web Animations). The trick with animations, in particular CSS animations, is that the browser knows up front exactly what the animation is. This means it can easy do the animation in the compositing thread (or process), without impacting the main thread (UI). Script-based timing functions invalidate this opportunity, since there is no guarantee on the amount of time the function takes to compute. Yes, you can reduce the side-effects by putting the timing function in an isolated Houdini world, but that still doesn't stop an infinite loop. This doesn't mean I'm against script-based timing functions (although I do think it in general it is more common to script the entire animation rather than just the timing function part). I just want to make it clear that a simple declarative time-bounded function is necessary, and probably solves 99% of use cases. -- GitHub Notification of comment by grorg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/229#issuecomment-241581785 using your GitHub account
Received on Monday, 22 August 2016 23:26:23 UTC