Hey Nikos, Sorry for the lack of overlap here, it is a bug caused by the 4->2 week release shift and is now fixed <https://github.com/GoogleChrome/chromium-dashboard/pull/6877> for new tokens. API owners have agreed that no approval is necessary for OT extension post approved I2S and we are discussing making that automatic in the tool <https://github.com/GoogleChrome/chromium-dashboard/issues/6875>. But until then, requests like this are being rubber stamp approved without need for discussion.
Cheers, Rick On Tue, Sep 15, 2026 at 5:34 PM Chromestatus < [email protected]> wrote: > *Contact emails* > [email protected] > > *Explainer* > https://github.com/WICG/cpu-performance > > *Specification* > https://wicg.github.io/cpu-performance > > *Summary* > Starting in Chrome 152, Chrome introduces the CPU Performance API, which > allows web applications to determine the CPU performance of a user's > device. This API targets web applications that will use this information to > provide an improved user experience, possibly in combination with the > Compute Pressure API, which provides information about the user device’s > CPU pressure or utilization and allows applications to react to changes in > CPU pressure. Users can override the reported performance using Chrome > browser **Settings > Performance > Speed > Override CPU performance tier**. > Administrators can also control this behavior using the > [CpuPerformanceTierOverride]( > https://chromeenterprise.google/policies/#CpuPerformanceTierOverride) > policy (which takes precedence over the user setting). For more details, > see [CPU Performance API Explainer]( > https://github.com/WICG/cpu-performance). > > *Blink component* > Blink>PerformanceAPIs > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EPerformanceAPIs%22> > > *Web Feature ID* > Missing feature > > *TAG review* > https://github.com/w3ctag/design-reviews/issues/1198 The specification is > ready for review, so the above is not an "early design" review. > > *TAG review status* > Pending > > *Origin Trial Name* > CPU Performance API > > *Goals for experimentation* > This API provides device-specific information about CPU performance while > preserving user privacy. We'd like to see if this information is useful in > providing the user experience improvement for the kind of applications that > this API targets and if its shape matches developer expectations. We will > measure API usage metrics and obtain developer feedback to validate our > designs. > > *Chromium Trial Name* > CpuPerformance > > *Origin Trial documentation link* > https://github.com/WICG/cpu-performance > > *WebFeature UseCounter name* > kNavigatorCPUPerformance > > *Risks* > > > *Interoperability and Compatibility* > None. > > *Gecko*: No signal ( > https://github.com/mozilla/standards-positions/issues/1364) > > *WebKit*: Oppose (https://github.com/WebKit/standards-positions/issues/622 > ) > > *Web developers*: Positive > > *Other signals*: Adobe: https://github.com/WICG/cpu-performance/issues/6 > Figma: > https://github.com/WICG/proposals/issues/253#issuecomment-3719833708 > > *WebView application risks* > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > None. > > > *Reason this experiment is being extended* > The API has shipped during the OT, 1st party consumers have not yet > upgraded en masse to 152, and we want to guarantee that there will be no > gap for the service. > > *Ongoing technical constraints* > None. > > *Debuggability* > Nothing interesting, debuggability review completed. > > *Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, ChromeOS, Android, and Android WebView)?* > Yes > > *Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* > Yes > > https://wpt.fyi/results/cpu-performance?label=experimental&label=master&aligned > > *Flag name on about://flags* > *No information provided* > > *Finch feature name* > CpuPerformance > > *Requires code in //chrome?* > True > > *Tracking bug* > https://issues.chromium.org/449760252 > > *Measurement* > > https://uma.googleplex.com/p/chrome/timeline_v2/?sid=eb11c4b156c799e994576301d01ff0b5 > > *Availability expectation* > Feature is available only in Chromium browsers. It is not clear if/when > other browsers will follow. > > *Adoption expectation* > Feature is used by specific partner(s) to provide functionality as of the > launch in Chrome. At least one major abstraction will replace their use of > an existing feature with this feature as of the launch. > > *Adoption plan* > We are already working with specific partner(s) who will benefit from this > feature. > > *Non-OSS dependencies* > > Does the feature depend on any code or APIs outside the Chromium open > source repository and its open-source dependencies to function? > None. > > *Estimated milestones* > Shipping on desktop 152 > Origin trial desktop first 146 > Origin trial desktop last 152 > Origin trial extension 1 end milestone 154 > Shipping on Android 152 > Origin trial Android first 146 > Origin trial Android last 152 > Shipping on WebView 152 > Origin trial WebView first 146 > Origin trial WebView last 152 > > *Anticipated spec changes* > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > No such open issues. > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/5189864286978048?gate=5149369488769024 > > *Links to previous Intent discussions* > Intent to Prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMHN%3DHydj6Q7pz6i_y3j1ON20a270NFGx%2BKD11Q3VdfTXvtCDg%40mail.gmail.com > Intent to Experiment: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69aaa531.2b0a0220.c2d7.063a.GAE%40google.com > Intent to Ship: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a26ce42.f2d2b681.29210.0178.GAE%40google.com > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com>. > > -- > 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/6aa9b9fa.fe15df9f.319a5c.0071.GAE%40google.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6aa9b9fa.fe15df9f.319a5c.0071.GAE%40google.com?utm_medium=email&utm_source=footer> > . > -- 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/CAFUtAY-fZ4xmUw8z0Bt4vpfun74ft626haVFOPvOs5Hz5VVKUA%40mail.gmail.com.
