On Monday, June 22, 2026 at 5:02:04 PM UTC+2 Rick Byers wrote: Regarding the interoperability concern <https://github.com/WICG/cpu-performance/issues/2>, I also built a JS reference implementation derived from the Chromium impl and proposed contributing it to the WICG <https://github.com/WICG/cpu-performance/pull/12>, along with a little demo page <https://rbyers.github.io/cpu-performance/demo.html>, and possible spec additions <https://github.com/WICG/cpu-performance/pull/13>. I suggest we give the standards debate a couple weeks to play out in the WICG repo + TAG thread. Then, depending on the outcome, API owners can evaluate whether to ask the team to move their implementation into an independent open source repo. IMHO if the spec ends up reasonably precisely defining the algorithm, there's no reason to request any changes in Chromium's implementation strategy.
Following the suggestion from last API owners' meeting, I added a new GitHub PR <https://github.com/WICG/cpu-performance/pull/19> with the full algorithm that Chromium uses, included as a normative part of the spec. This should be seen as an alternative option to Rick's partial algorithm <https://github.com/WICG/cpu-performance/pull/13>. The intention is to hear the opinion of other potential implementors and finally choose the option that best resolves the interoperability concern. -- 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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/984c25f1-cb65-49bb-9da2-f1e1f30b1e12n%40chromium.org.
