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

[bugzilla-daemon at webkit.org]

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

--- Comment #29 from mdrejhon <mark at blurbusters.com> ---
Update, I now realize you meant Web Animation API rather than requestAnimationFrame():

> If other browsers are passing a timestamp to WEB ANIMATION API which is not just the "now" timestamp from the HTML spec, and this different timestamp gives you additional information, then you should lobby for those browsers to standardize whatever they are doing.

Perhaps that is the new insight. While requestAnimationFrame is working perfectly with correctly synonymous now()=refresh timestamps in all major browsers (except 120Hz Safari -- that is when we pull hair & throw keyboards)

You're right -- we may have just very well discovered an inconsistency between different browsers' handling of Web Animation API timestamps.  We now need to test all majors and see why it deviates from behavior of requestAnimiationFrame in non-synonymous "now() identical to refresh cycle timestamp" behavior, since that's literally just 2+2=5 in VSYNC science...

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