https://github.com/w3c/compute-pressure/blob/main/README.md
https://www.w3.org/TR/compute-pressure
https://developer.chrome.com/origintrials/#/view_trial/1196831600973709313
The Compute Pressure API offers high-level states that represent the pressure on the system. It allows the implementation to use the right underlying hardware metrics to ensure that users can take advantage of all the processing power available to them as long as the system is not under unmanageable stress. “Pressure” is a generic term by design – at the moment it is calculated based on CPU load, but future plans include using signals from temperature and battery status, for example.
We would like to extend the current Origin Trial from M120 to M123 (inclusive).
Blink>PerformanceAPIs>ComputePressure
spec review: https://github.com/w3ctag/design-reviews/issues/795 wide review tracker: https://github.com/w3c/compute-pressure/issues/177
Issues addressed
ComputePressure_v2
https://developer.chrome.com/docs/web-platform/compute-pressure/
ComputePressure
https://github.com/oyiptong/compute-pressure/blob/main/README.md
Gecko: No signal (https://github.com/mozilla/standards-positions/issues/521)
WebKit: Negative (https://lists.webkit.org/pipermail/webkit-dev/2021-May/031845.html) This issue has been taken into account: https://github.com/w3c/compute-pressure/issues/24
Web developers: Positive (https://github.com/w3c/compute-pressure/issues/14)
Other signals:
https://github.com/w3c/compute-pressure/issues/79
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
We propose extending the “Compute Pressure API” Origin Trial. We decided to extend the experiment based on feedback from users and a need for wider testing with 3rd-party Origin Trial tokens.
One of the features of this API is that it can provide data to iframe's, even cross-origin ones, under certain circumstances. That is due to the fact that many video conferencing services provide an SDK to their users based on embedding the 3rd party code via an iframe. It was reported that this didn't work with the current origin trial, unless both the SDK and the embedder ask for individual tokens, which is not scalable across a number of sites, limiting the usefulness of the origin trial.
It is now possible to use a third-party origin trial instead which makes it possible for providers of embedded content to try out a new feature across multiple sites. For this reason we are requesting an extension.
Furthermore, the specification has been modified to support workers in the privacy algorithms. The implementation will be merged to chromium for M122 and should also be evaluated by the API users.
Supported to Windows, Mac, Linux, ChromeOS.
Support on Android (incl. Android WebView) has been deprioritized as there is no current way to access the telemetry needed after Android 11, and the current partners we are engaging with have no need as they are using native solutions on Android at this point.
Yes
https://github.com/w3c/compute-pressure/blob/main/HOWTO.md
see https://github.com/w3c/compute-pressure/blob/main/HOWTO.md
None
None
False
OriginTrial desktop last (new request) |
|
123 |
OriginTrial desktop last |
|
118 |
OriginTrial desktop first |
|
115 |
OriginTrial desktop last |
|
94 |
OriginTrial desktop first |
|
92 |
DevTrial on desktop |
|
109 |
https://chromestatus.com/feature/5597608644968448
Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/LTIRZ24C5Os/m/BPSeJ8y0BwAJ Ready for Trial: https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/-1ciwdn23J4
Intent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/QfJ4pngu3gc
Intent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/HzVV-sM97T0
Intent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/QfJ4pngu3gc/
--
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 blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/BY5PR11MB40694670568F3D61825DD8929386A%40BY5PR11MB4069.namprd11.prod.outlook.com.
Hi,Can you please request review for the security, privacy and debuggability bits now in the chromestatus tool? Perhaps there's some history somewhere you can point at from the first OT?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8cJHWCtL7b4ec_-xbYZBYjE5w6trzG7GtTnVX1xqs8LQ%40mail.gmail.com.
Yep - all good to go.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/78b8fff5-e5b9-4579-b038-c4d3527514afn%40chromium.org.