[Webkit-unassigned] [Bug 173434] Support for 120Hz requestAnimationFrame (Compliance with HTML 5.2 DRAFT 8)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=173434

--- Comment #2 from mdrejhon <mark at blurbusters.com> ---
A comment was made by someone that 120fps and higher would ideally be done via a user request (like .requestFullScreen() API).   

If this is absolutely necessary to ask the user, discoverability of refresh rate should be provided (e.g. returns "120"), along with discoverability of a throttle (e.g. returns "60").   

Consensus in talks indicates improved discoverability is essential.  It is necessary to inform the JavaScript applications what the refresh rate is, and what the current throttle is (awareness of running animations at lower than refresh rate).  Currently, this is impossible -- several websites such as http://www.testufo.com relies on heuristics to discover the current refresh rate -- but this can be completely impossible in the very few browsers (such as iPad 120Hz Safari) throttled/locked to the assumption of 60 animation callbacks per second regardless of refresh rate.

This discoverability of refresh rate & animation throttles would be put in as part of Phase 1 of the pending W3C HTML work, issue #375

VSYNC & Refresh Rate extensions to HTML standard:
PHASE 1 -- Discoverability -- https://github.com/w3c/html/issues/375#issuecomment-306591154
PHASE 2 -- New API changes -- https://github.com/w3c/html/issues/375#issuecomment-306603305

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170712/e6404951/attachment-0001.html>