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

[bugzilla-daemon at webkit.org]

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

--- Comment #21 from mdrejhon <mark at blurbusters.com> ---
Web Animation API is missing a mandatory capability that we require to continue to be peer-reviewed (we are in over 25+ peer reviewed papers)

We need single-framedrop detection capability (e.g. running at 59fps at 60Hz, or running at 239fps at 240Hz).  To fix this, requires an animation-frame presentation callback as part of Web Animation API, e.g. the exact (relative-time) now() moment that a frame is presented from OS to GPU driver, e.g. Present() or glxxSwapBuffers() or similar page flip / frame buffer blit is called.  

requestAnimationFrame() provides such information, while Web Animation API does not.

Because of this, Web Animation API produces lower-science-quality results, especially when a camera is pointed at a TestUFO animation (part of a NIST.gov peer reviewed paper)

Even for effects almost visible to human eye, but visible in camera photographs;

More information:
https://github.com/WebKit/explainers/issues/85#issuecomment-1203341375

-- 
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/fdfa4518/attachment.htm>