Arnaud (Arno) Mandy

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...

@Elchi3, you are correct, the implementation is relative to the Unix Epoch (January 1, 1970, UTC). The question is now, what would make more sense? To use Unix Epoch, or...

Yes, Thanks for pointing out the discussion! As you mentioned, Unix Epoch is also valid with [DOMHighResTimeStamp](https://w3c.github.io/hr-time/#sec-domhighrestimestamp). @kenchris let s look at a better wording together.

Specs are clear, implementation is not. It is now tracked here: [crbug](https://issues.chromium.org/issues/336140984)

closing spec issue, now that we have an implementation bug

@brycepj The Compute Pressure API was released on Chromium M125. Did you try it with Slack? Do you have any experience to share with us?

@brycepj Great to hear that! Thanks. "thermal" source is not yet supported, since we haven't found yet a good generic way to support it accross platforms and OSes. At the...

1) I find it a bit strange that the creation of the virtual source also defines the sample array. Should we restrict the creation to only create the virtual source?...

One major change we forgot in this PR: Raphael as an Editor. :)

We have started to evaluate a possible implementation on Chromium, this work will continue in Q2.