- From: Mark Rejhon <mark@blurbusters.com>
- Date: Thu, 22 Aug 2013 01:16:35 -0400
- To: public-web-perf@w3.org
- Cc: zhiqiang.zhang@intel.com, pan.deng@intel.com
Received on Thursday, 22 August 2013 05:17:02 UTC
>>"Review is appreciated, Zhiqiang Zhang will address any feedback." Just to let you know, Modern tests for requestAnimationFrame() should not assume that the computer monitor operates at 60Hz. As of year 2013, all 5 major web browsers synchronize rAF() to refresh rate, with some minor exceptions. (See http://www.testufo.com/browser.html for a list of supported browsers) This should now be incorporated as part of modern tests for rAF(), as some websites such as www.testufo.com now depend on rAF() synchronizing to refresh rate. I posted a link to an Excel spreadsheet of my testing of requestAnimationFrame. As an example, one of the browsers throttles requestAnimationFrame() when above a specific refresh rates. Please make sure that all future rAF() test suites including testing rAF() support at a wide variety of refresh rates. Some example cases: -- Laptops slowing refresh rate to 50Hz during power management -- Some SEIKI 4K users are using 30Hz during 3840x2160 -- Gaming 120Hz and 144hz computer monitors. Most browsers pass these test cases, but not all of them; tests should check for successful rAF() synchronization to refresh rate. Thanks, Mark Rejhon
Received on Thursday, 22 August 2013 05:17:02 UTC