Extending from M117 to M118 LGTM.

-mike


On Fri, May 12, 2023 at 7:14 AM 'Ajay Rahatekar' via blink-dev <
[email protected]> wrote:

> Hello API Owners,
>
> The Intent to Experiment mentions Origin Trial duration of M115 - M117. We
> would like approval to have the Origin Trial for M115 - M118 based on the
> current 4 week Chrome release cycle.
>
> Thanks in advance.
>
> -Ajay
>
> On Tuesday, May 2, 2023 at 10:28:08 PM UTC-7 [email protected] wrote:
>
>> Great! Thank you!
>>
>> Arno
>>
>> ------------------------------
>> *From:* Ajay Rahatekar <[email protected]>
>> *Sent:* Tuesday, May 2, 2023 20:52
>> *To:* blink-dev <[email protected]>
>> *Cc:* [email protected] <[email protected]>; Mandy, Arnaud <
>> [email protected]>; Christiansen, Kenneth R <[email protected]>;
>> Wang, Wei4 <[email protected]>; Ajay Rahatekar <[email protected]>
>> *Subject:* Re: [blink-dev] Re: Intent to Experiment: Compute Pressure
>>
>> Ty, Mike.
>>
>> On Tuesday, May 2, 2023 at 10:51:55 AM UTC-7 [email protected] wrote:
>>
>> Apologies for this slipping through the cracks.
>>
>> LGTM to experiment from M115 to M117.
>> On 5/1/23 6:15 PM, 'Ajay Rahatekar' via blink-dev wrote:
>>
>> [email protected]
>>
>> Friendly ping for review.
>>
>> On Thursday, April 20, 2023 at 3:20:21 AM UTC-7 [email protected]
>> wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> * Contact emails [email protected], [email protected],
>> [email protected] Explainer
>> https://github.com/w3c/compute-pressure/blob/main/README.md
>> <https://github.com/w3c/compute-pressure/blob/main/README.md> Specification
>> https://www.w3.org/TR/compute-pressure
>> <https://www.w3.org/TR/compute-pressure> Design docs
>> https://developer.chrome.com/docs/web-platform/compute-pressure
>> <https://developer.chrome.com/docs/web-platform/compute-pressure> 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. Blink component
>> Blink>PerformanceAPIs>ComputePressure Search tags compute pressure TAG
>> review spec review: https://github.com/w3ctag/design-reviews/issues/795
>> <https://github.com/w3ctag/design-reviews/issues/795> wide review tracker:
>> https://github.com/w3c/compute-pressure/issues/177
>> <https://github.com/w3c/compute-pressure/issues/177> TAG review status
>> Issues addressed
>> https://github.com/w3ctag/design-reviews/issues/795#issuecomment-1513997968
>> <https://github.com/w3ctag/design-reviews/issues/795#issuecomment-1513997968>
>> Risks Interoperability and Compatibility Gecko: No signal
>> (https://github.com/mozilla/standards-positions/issues/521
>> <https://github.com/mozilla/standards-positions/issues/521>) WebKit:
>> Negative
>> (https://lists.webkit.org/pipermail/webkit-dev/2021-May/031845.html
>> <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
>> <https://github.com/w3c/compute-pressure/issues/24> Web developers:
>> Positive (https://github.com/w3c/compute-pressure/issues/14
>> <https://github.com/w3c/compute-pressure/issues/14>) Security
>> https://github.com/w3c/compute-pressure/issues/79
>> <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?
>> Goals for experimentation We want developer feedback around the feature's
>> performance and applicability in real usage scenarios.   The API shape has
>> changed significantly since the first Origin Trial (M92-M94), and we would
>> like to get additional developer feedback before shipping.
>> https://github.com/w3c/compute-pressure/blob/main/CHANGES.md
>> <https://github.com/w3c/compute-pressure/blob/main/CHANGES.md> Ongoing
>> technical constraints Debuggability Will this feature be supported on all
>> six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android
>> WebView)? No, supported for Windows, Mac, Linux, Chrome OS. Is this feature
>> fully tested by web-platform-tests? Yes
>> https://wpt.fyi/results/compute-pressure?label=master&label=experimental&aligned&view=subtest&q=compute-pressure
>> <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
>> <https://github.com/w3c/compute-pressure/blob/main/HOWTO.md> Flag name
>> --enable-features=ComputePressure see
>> https://github.com/w3c/compute-pressure/blob/main/HOWTO.md
>> <https://github.com/w3c/compute-pressure/blob/main/HOWTO.md> Requires code
>> in //chrome? False Tracking bug https://crbug.com/1067627
>> <https://crbug.com/1067627> Launch bug https://crbug.com/1173266
>> <https://crbug.com/1173266> Estimated milestones We hope to start the
>> Origin Trial sometime during M115 beta. We plan to continue the Origin
>> Trial until the end of M117 to give developers time to test the API and
>> provide feedback. Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5597608644968448
>> <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
>> <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
>> <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/HzVV-sM97T0
>> <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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/259034fd-21b0-43fd-bd25-c9e361a625ecn%40chromium.org
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/259034fd-21b0-43fd-bd25-c9e361a625ecn%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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/da53c89f-4c68-4609-96e1-7412583f0470n%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/da53c89f-4c68-4609-96e1-7412583f0470n%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3De%2BLu1Jv4HuCw1tD4DbyXMUjT4U2FT1seEkG3G6beXZjA%40mail.gmail.com.

Reply via email to