Hi, Correction on the previous Ready for Trial email: Debuggability : chrome-internals://compute-pressure *is not existing.*
Apoligizing for the confusion. Br Arnaud On Wednesday, December 21, 2022 at 12:23:24 PM UTC+2 Arnaud Mandy wrote: > Contact emails kenneth.r.c...@intel.com > > Explainer https://github.com/WICG/compute-pressure/blob/main/README.md > > Specification https://www.w3.org/TR/compute-pressure > > Summary > > Provides a way for websites to react to changes in the CPU pressure of the > target device, such that websites can trade off resources for an improved > user experience. > > > Blink component Blink>PerformanceAPIs>ComputePressure > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPerformanceAPIs%3EComputePressure> > > Search tags compute pressure > <https://chromestatus.com/features#tags:compute%20pressure> > > TAG review > > TAG review status Pending > > Risks > > > Interoperability and Compatibility > > > > *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/WICG/compute-pressure/issues/24 > > *Web developers*: No signals > > *Other signals*: > > Security > > https://github.com/WICG/compute-pressure/issues/79 > > > 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? > > > > Goals for experimentation > > This API provides device-specific information and has been designed to > provide useful and actionable metrics while preserving user privacy. We'd > like to see if the information provided provides the user experience > improvement sought after and if the shape matches developer expectations. > We will measure API usage metrics and obtain developer feedback to validate > our designs. We'll focus on feedback on UX changes on lower-powered devices > specifically. > > > Ongoing technical constraints > > > > Debuggability > > chrome-internals://compute-pressure > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? No > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? Yes > > DevTrial instructions > https://github.com/WICG/compute-pressure/blob/main/HOWTO.md > > Flag name see https://github.com/WICG/compute-pressure/blob/main/HOWTO.md > > Requires code in //chrome? False > > Tracking bug https://crbug.com/1067627 > > Launch bug https://crbug.com/1173266 > > Estimated milestones > DevTrial on desktop 109 > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5597608644968448 > > Links to previous Intent discussions Intent to prototype: > https://groups.google.com/a/chromium.org/g/blink-dev/c/LTIRZ24C5Os/m/BPSeJ8y0BwAJ > Intent to Experiment: > https://groups.google.com/a/chromium.org/g/blink-dev/c/HzVV-sM97T0 > > -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fb140460-2269-4123-86ee-42f53cf1944bn%40chromium.org.
