[Webkit-unassigned] [Bug 173434] Support for 120Hz requestAnimationFrame

[bugzilla-daemon at webkit.org]

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

--- Comment #24 from mdrejhon <mark at blurbusters.com> ---
Additional Note (for those unfamiliar with existence of A leads to existence of B)

I should also add that it ends up being a very accurate refresh cycle timestamp by the virtue of requestAnimationFrame() being specified in W3C section 7.1.4.2.  The fact that browsers are effectively VSYNC ON means frame presentation blocks until a refresh cycle, and then immediately after, the engine calls requestAnimationFrame() callback for rendering the next frame.  The fact that it's called immediately after the refresh cycle unblocks the previous frame, means I've got scientifically accurate refresh cycle timestamps

The algorithm works correctly on Apple devices at 60Hz actually -- indeed it works correctly on Apple devices at 60Hz, but not at 120Hz (because you don't allow requestAnimationFrame to work at 120fps 120Hz in Safari)

See the Catch-22?

-- 
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/20220803/79632aaf/attachment.htm>