[Webkit-unassigned] [Bug 228137] Improve timer precision when cross-origin isolated via COOP+COEP

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 27 10:49:23 PDT 2021


--- Comment #6 from Chris Dumez <cdumez at apple.com> ---
(In reply to Chris Dumez from comment #5)
> According to
> https://developer.chrome.com/blog/cross-origin-isolated-hr-timers/ and blink
> code inspection, it looks like Chrome is using 100us precision in general
> and 5ns when cross-origin isolated.
> It looks like WebKit is using a much higher 1ms precision in general
> currently.
> I guess we need to decide what precision we want to use when
> cross-origin-isolated. Do we want to go back to 100us, like before r226495?
> It would still make us nowhere near Chrome in terms of precision.

Looks like Gecko is using 1ms for general precision and 20us for cross-origin-isolated precision.

Maybe we should at least match Gecko from cross-origin-isolated precision?

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

More information about the webkit-unassigned mailing list