Could someone elaborate on why this won't be implemented for Android? It seems like a very useful thing to have, especially considering that the biggest amount of users with low end hardware who would stand to benefit are on Android.
"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." I see a variety of CPU monitoring apps in the Play Store. Could someone test if they work on Android >=12? Also, how can it be both that new Android versions don't allow access and partners are using native solutions? Why can't Chromium use whatever they are using? On Monday, May 20, 2024 at 7:00:18 AM UTC-4 Arnaud Mandy wrote: > Philip, > > Thanks for the follow up. > Yes, you are correct! > > I ll file a bug and propose a fix (disabling feature on Android). > > Arnaud. > > On Friday, May 17, 2024 at 6:00:20 PM UTC+3 Philip Jägenstedt wrote: > >> Hi Arnaud, >> >> I have a followup question about this. I assumed that the feature >> wouldn't be enabled on Android, but judging by Chromium source and wpt.fyi >> test results, at least the API surface is exposed: >> >> https://wpt.fyi/results/compute-pressure/idlharness.https.any.html?label=master&label=experimental&product=chrome&product=chrome_android&aligned >> >> What will be the behavior on Android, will the API appear to work but >> never invoke the observer callback? If so, would it make sense to disable >> the feature on Android instead? >> >> Best regards, >> Philip >> >> On Tue, Mar 19, 2024 at 9:52 PM Chris Harrelson <chri...@chromium.org> >> wrote: >> >>> LGTM3 >>> >>> On Mon, Mar 18, 2024 at 6:10 AM Arnaud Mandy <arnaud...@intel.com> >>> wrote: >>> >>>> Shipping of Compute Pressure API has been changed from M124 to M125. >>>> Today is M124 branching and we are not fulfilling all the requirements >>>> for shipping given the ongoing discussions, the filed issue >>>> <https://github.com/w3c/compute-pressure/issues/253>, and one missing >>>> LGTM. >>>> We are still actively working on the items just mentioned to see >>>> Compute Pressure API shipping in M125. >>>> >>>> Br, >>>> Arnaud >>>> On Tuesday, March 5, 2024 at 1:57:31 PM UTC+2 Arnaud Mandy wrote: >>>> >>>>> Contact emails >>>>> >>>>> kenneth.r.c...@intel.com, arnaud...@intel.com, wei4...@intel.com, >>>>> raphael.ku...@intel.com >>>>> >>>>> Explainer >>>>> >>>>> https://github.com/w3c/compute-pressure/blob/main/README.md >>>>> >>>>> Specification >>>>> >>>>> https://www.w3.org/TR/compute-pressure >>>>> >>>>> Summary >>>>> >>>>> The Compute Pressure API offers high-level states that represent the >>>>> pressure on the system. It allows the implementation to use underlying >>>>> hardware/platform metrics to inform the API users of possible stress >>>>> (high >>>>> CPU load at the moment) on the system and consequently take the >>>>> corrective >>>>> actions needed. >>>>> >>>>> “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. >>>>> >>>>> https://developer.chrome.com/docs/web-platform/compute-pressure/ >>>>> >>>>> 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 >>>>> >>>>> spec review: https://github.com/w3ctag/design-reviews/issues/795 >>>>> >>>>> wide review tracker: >>>>> https://github.com/w3c/compute-pressure/issues/177 >>>>> >>>>> TAG review status >>>>> >>>>> Issues addressed >>>>> >>>>> Chromium Trial Name >>>>> >>>>> ComputePressure >>>>> >>>>> Origin Trial documentation link >>>>> >>>>> https://developer.chrome.com/docs/web-platform/compute-pressure/ >>>>> >>>>> Origin Trials history >>>>> >>>>> The first Origin Trial >>>>> <https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/HzVV-sM97T0/m/3pQ311KHAAAJ> >>>>> was >>>>> run between M92-94. >>>>> >>>>> The Compute Pressure API was widely redesigned after this OT to >>>>> resemble existing observer-based web APIs and also to provide better >>>>> privacy and security guarantees after discussions with PING. >>>>> >>>>> The second Origin Trial >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/QfJ4pngu3gc> took >>>>> place during M115-M120. >>>>> During this origin trial we realized that the full capacity of the API >>>>> couldn’t be tested due to a lack of support for third-party tokens. An >>>>> Origin >>>>> Trial extension >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/s83S7wXxa6E/m/AjvsIJxmAQAJ> >>>>> was >>>>> necessary until M123. >>>>> >>>>> 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/w3c/compute-pressure/issues/24 >>>>> >>>>> *Web developers*: Positive ( >>>>> https://github.com/w3c/compute-pressure/issues/14) >>>>> >>>>> *Other signals*: >>>>> >>>>> Security >>>>> >>>>> https://github.com/w3c/compute-pressure/issues/79 >>>>> >>>>> WebView application risks >>>>> >>>>> No >>>>> >>>>> Debuggability >>>>> >>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>> Mac, Linux, ChromeOS, Android, and Android WebView)? >>>>> >>>>> No, >>>>> Windows, Linux, ChromeOs, Mac. >>>>> >>>>> 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. >>>>> >>>>> 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/compute-pressure?run_id=5116280230641664 >>>>> >>>>> The wpt.fyi results are flaky due to WPT bug 44438 >>>>> <https://github.com/web-platform-tests/wpt/issues/44438> >>>>> >>>>> DevTrial instructions >>>>> >>>>> https://github.com/w3c/compute-pressure/blob/main/HOWTO.md >>>>> >>>>> Flag name on chrome://flags >>>>> >>>>> see https://github.com/w3c/compute-pressure/blob/main/HOWTO.md >>>>> >>>>> Finch feature name >>>>> >>>>> None >>>>> >>>>> Non-finch justification >>>>> >>>>> None >>>>> >>>>> Requires code in //chrome? >>>>> >>>>> False >>>>> >>>>> Tracking bug >>>>> >>>>> https://crbug.com/1067627 >>>>> >>>>> Launch bug >>>>> >>>>> https://crbug.com/1173266 >>>>> >>>>> Sample links >>>>> https://w3c.github.io/compute-pressure/demo >>>>> >>>>> Estimated milestones >>>>> >>>>> OriginTrial desktop extension >>>>> >>>>> 123 >>>>> >>>>> OriginTrial desktop last >>>>> >>>>> 118 >>>>> >>>>> OriginTrial desktop first >>>>> >>>>> 115 >>>>> >>>>> OriginTrial desktop last >>>>> >>>>> 94 >>>>> >>>>> OriginTrial desktop first >>>>> >>>>> 92 >>>>> >>>>> DevTrial on desktop >>>>> >>>>> 109 >>>>> >>>>> Anticipated spec changes >>>>> >>>>> None >>>>> >>>>> 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 >>>>> >>>>> 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 Extend Experiment: >>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/s83S7wXxa6E/m/AjvsIJxmAQAJ >>>>> >>>>> >>>>> 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 blink-dev+...@chromium.org. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7c4c2393-3c8c-4257-88f2-cf351e74a650n%40chromium.org >>>> >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7c4c2393-3c8c-4257-88f2-cf351e74a650n%40chromium.org?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 blink-dev+...@chromium.org. >>> >> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8f%2BaUZAMx1qiGv2CxBXY1vcqQ1Ot%3DU63My98gem9x3_w%40mail.gmail.com >>> >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8f%2BaUZAMx1qiGv2CxBXY1vcqQ1Ot%3DU63My98gem9x3_w%40mail.gmail.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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/796196c5-2e48-4b04-a2f5-51e17d673df4n%40chromium.org.
