Thanks, yeah the chromestatus UI is new so it's a little more formal now but not a new requirement.
LGTM for API owners. But you'll need to confirm approval from security and privacy before extending the OT. On Thu, Dec 7, 2023 at 1:38 PM Arnaud Mandy <[email protected]> wrote: > @chris @rick, Thanks for the comments, it seems to be a new process. > > We had gone through these privacy and security checks before, but not with > the new chromestatus interface. > > We've been requesting approval from privacy, security and also > debuggability teams on chromestatus now. > > Arnaud > > > On Wednesday, December 6, 2023 at 6:57:09 PM UTC+2 Chris Harrelson wrote: > >> On Tue, Dec 5, 2023 at 11:20 AM Rick Byers <[email protected]> wrote: >> >>> 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? >>> >> >> I think you also need to request API owners review, the intent isn't >> showing up properly in our dashboard. >> >> >>> >>> Otherwise, seems reasonable to extend to me. >>> >>> Rick >>> >>> >>> On Mon, Dec 4, 2023 at 1:59 PM Mandy, Arnaud <[email protected]> >>> wrote: >>> >>>> Contact emails [email protected], [email protected], >>>> [email protected], [email protected] >>>> >>>> >>>> Original I2E >>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/QfJ4pngu3gc/ >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/QfJ4pngu3gc/m/CPQnKtqoAgAJ> >>>> >>>> Explainer >>>> >>>> https://github.com/w3c/compute-pressure/blob/main/README.md >>>> >>>> >>>> Specification >>>> >>>> https://www.w3.org/TR/compute-pressure >>>> >>>> >>>> Origin Trial >>>> >>>> >>>> https://developer.chrome.com/origintrials/#/view_trial/1196831600973709313 >>>> >>>> >>>> Summary >>>> >>>> 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 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_v2 >>>> >>>> >>>> Origin Trial documentation link >>>> >>>> https://developer.chrome.com/docs/web-platform/compute-pressure/ >>>> >>>> >>>> Chromium Trial Name >>>> >>>> ComputePressure >>>> >>>> >>>> Origin Trial documentation link >>>> >>>> https://github.com/oyiptong/compute-pressure/blob/main/README.md >>>> >>>> >>>> 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 >>>> >>>> *Does this intent deprecate or change behavior of existing APIs, such >>>> that it has potentially high risk for Android WebView-based applications?* >>>> >>>> >>>> >>>> Motivation For Requesting Extension. >>>> >>>> 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 >>>> <https://w3c.github.io/compute-pressure/#dfn-document-has-implicit-focus>. >>>> 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 >>>> <https://web.dev/articles/third-party-origin-trials> 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 >>>> <https://github.com/w3c/compute-pressure/pull/238> 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. >>>> >>>> >>>> Ongoing technical constraints >>>> >>>> >>>> Will this feature be supported on all six Blink platforms (Windows, >>>> Mac, Linux, ChromeOS, Android, and Android WebView)? >>>> >>>> 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. >>>> >>>> >>>> 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?label=master&label=experimental&aligned&view=subtest&q=compute-pressure >>>> >>>> >>>> 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 >>>> >>>> >>>> Estimated milestones >>>> 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 >>>> >>>> >>>> >>>> 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 Experiment: >>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/QfJ4pngu3gc/ >>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/QfJ4pngu3gc/m/CPQnKtqoAgAJ> >>>> >>>> >>>> >>>> -- >>>> 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 on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/BY5PR11MB40694670568F3D61825DD8929386A%40BY5PR11MB4069.namprd11.prod.outlook.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/BY5PR11MB40694670568F3D61825DD8929386A%40BY5PR11MB4069.namprd11.prod.outlook.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 on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8cJHWCtL7b4ec_-xbYZBYjE5w6trzG7GtTnVX1xqs8LQ%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8cJHWCtL7b4ec_-xbYZBYjE5w6trzG7GtTnVX1xqs8LQ%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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY8LJRqWbvB68mcn4ZVuxLzkVDsKyqe7qRSySycsf3xTzQ%40mail.gmail.com.
