As of Chrome M120, the timestamps passed to the requestAnimationFrame() callback and the timestamp returned by document.timeline.currentTime would be coarsened according to the rules specified in https://w3c.github.io/hr-time/#dfn-coarsen-time/. This means that in cross-origin isolated contexts, those timestamps would have a resolution of 5 microseconds. Coarsening these timestamps is aligned with current Gecko & WebKit behavior (WebKit aligns those timestamps to a whole millisecond), and is specified in the HTML standard.
Authors that rely on these timestamps to be super-high-resolution in Chromium should now expect them to be slightly coarser -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYY05efbzeSNpNb4RPgBPns_Ur7aLc5hKmTzWzLLoKOHMQ%40mail.gmail.com.
