- From: Kyle Simpson <getify@gmail.com>
- Date: Mon, 13 Jun 2011 08:36:46 -0500
- To: <public-web-perf@w3.org>
At the TXJS conference over the weekend, several talks were dedicated to the topic of using CSS transitions and animations to replace the more clunky (and often less performant) JavaScript animation approaches of many "effects" done on web pages. But, noted was that not all systems benefit from this approach (namely, those which do not have the ability to hardware accelerate such things). The observation is that libraries like Scripty2 (and others) which try to detect which (best) animation method(s) to use could benefit from an interface in the content-JavaScript which allows them to detect such things: - are CSS transitions/animations hardware accelerated - what is the (avg/min/max) framerate of the transitions/animations on the page (the currently executing one and/or the most recently executed one) - the CPU usage stats for the current or previous animation(s) - etc The benefit for this type of information is that a library author can determine from such stats that a device will or won't (likely) benefit from offloading an animation to CSS as opposed to JavaScript (setInterval() or requestAnimationFrame, etc). I just wanted to ask if such data is already exposed, or planned to be exposed, in any interface, or if it's agreed that this type of data would be useful and relevant to expose to the JavaScript layer? --Kyle
Received on Monday, 13 June 2011 13:37:30 UTC