Thanks for these reproductions! I was able to quickly confirm that this is a result of us reporting coarse granularity in our timestamps. Based on the age of the github issue, I don't think it's related to our (recent) requestAnimationFrame timestamp clamping. It would be interesting to figure out what API in particular that's causing the issue and how it's being used. (It's probably performance.now() and I'm curious why it's causing the issue and if Unity could refactor to avoid this...)
Bug 1589060 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for these reproductions! I was able to quickly confirm that this is a result of us reporting coarse granularity in our timestamps. You can confirm by disabling RFP and setting `privacy.resistFingerprinting.reduceTimerPrecision.microseconds` to 100000 (which is RFP's value). Based on the age of the github issue, I don't think it's related to our (recent) requestAnimationFrame timestamp clamping. It would be interesting to figure out what API in particular that's causing the issue and how it's being used. (It's probably performance.now() and I'm curious why it's causing the issue and if Unity could refactor to avoid this...)