- From: Arnaud (Arno) Mandy via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Apr 2024 12:59:17 +0000
- To: public-device-apis-log@w3.org
About the implementation (on Chromium): The difference is that PerformanceObserver is getting the time from "TickClocks class", which is for iframe (e.g), relative to the time of creation of the frame, threfore the number is smaller in your experience. In ComputePressure it s the current time. (Which might be affected by the system). Unless mistaken, they are both DOMHighResTimeStamp. It makes no difference to us if the observer is run from a worker or a frame since the sample time is fetch from the same backend. I need to test out what would be the effect if using TickClocks instead of Time class in Chromium. Actually it would prevent the possible issue from system adjustment. -- GitHub Notification of comment by arskama Please view or discuss this issue at https://github.com/w3c/compute-pressure/issues/257#issuecomment-2031978278 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 April 2024 12:59:18 UTC