on this experiment be shifted, and >> instead of the originally requested period of m122-m127 (inclusive), we >> consider it retroactively as m124-m129 (inclusive

LGTM to experiment from 126 to 127 inclusive. On 5/7/24 10:52 AM, Chris Fredrickson wrote: > > Contact emails > > johannhof@chromium.org, cfredric@chromium.org, yigu

Does this intent deprecate or change behavior of existing APIs, such >>> that it has potentially high risk for Android WebView-based applications? >>> >>

LGTM to experiment for M126-M129. On Wed, Apr 24, 2024 at 9:08 AM Christian Biesinger wrote: > Sorry about that, done. > > On Wed, Apr 24, 2024 at 11:52 AM Chris Harrelson >

sent this intent before the feature was ready, and this required a lot of UX work, so trial has not started. Our plan is to start on Chrome M126 so I will assume the approvals are shifted

extend the experiment given developers need more time to >>> onboard and to keep experimenting with new features. We >>> would like to request extending the end

LGTM to experiment from M124 to M127 inclusive. >> On 2/26/24 5:45 PM, Yi Gu wrote: >> >> Contact emails >> >> >> * yigu@chromium.org , cbiesinger

LGTM to experiment for 4 milestones (125 to 128 inclusive OR 126 to 129 > inclusive). > > > On 4/1/24 2:13 PM, Menard, Alexis wrote: > > Hi, > > I think 4 milestones

> independent intent to make it include the new policy or not. > > Thanks, > Ming > > On Tue, Jan 16, 2024 at 2:35 PM Yoav Weiss wrote: > >> LGTM to experiment

LGTM to experiment 6 milestones from M125 to M130 inclusive > (which I think is what you asked for!). > > > On Thu, Mar 21, 2024 at 2:44 PM Mike Taylor > wrote: > >>

> The intent process only allows extensions of 3 milestones at a time. It also requires evidence of substantial progress on the feature. It sounds like here, the original experiment

>> experiment with it. >>> >>> The current status of the proposal and our experiments >>> >>> is as follows: >>> >>

> > Intent to Prototype > > https://groups.google.com/a/chromium.org/g/blink-dev/c/inRN8tI49O0 > > Intent to Experiment > > https://groups.google

In this experiment the only sites impacted are Google owned > domains which include the some domains > when > they are loaded in a third party context. > > For those requests

to an Intent to Ship sounds good. Can you update the process stage in the ChromeStatus tool, fill out any necessary fields that differ between the stages, and either start a new thread

> This experiment exposes a temporary set of APIs which provide access to > browser-determined treatment and control groups to support opt-in server > side testing of the

> This intent was updated to last between M123-M132 after > posting, but before approval. Since it's not clear whether you > looked at Chromestatus or the email thread

of this intent-to-experiment. > Estimated milestones > > DevTrial on desktop > > 123 And you should define the OriginTrial first and last milestones. Cheers, Rego

>> Intent to Prototype >>>>> >>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/inRN8tI49O0 >>>>>

before the Intent to Ship , that shouldn't be a problem. > > BTW, can you send the LGTM again? I forgot to cc blink-dev in my initial > reply and the LGTM was sent only to my email

Does this intent deprecate or change behavior of existing APIs, such > that it has potentially high risk for Android WebView-based applications? > > None > > > >

running this experiment from 120 through 123 >>>>>>>> inclusive, but may have to delay start to 121 running through 124. >>>>>>>

good to experiment with to me. But the key question is who is >> actually going to test it out in production? You mention "no signals" for >> web developer interest

dev] Intent to Extend Experiment: Compute Pressure API +1. Thanks Arnaud! On Tue, Dec 19, 2023 at 10:37 AM Mike Taylor > wrote: Yep - all good to go. On 12/19/23 4:18 AM, Arnaud Mandy

LGTM to experiment from M116 to M119 inclusive. >> On 6/1/23 3:19 AM, 'Arthur Hemery' via blink-dev wrote: >> >> Contact emails ahe...@chromium.org

LGTM to experiment from M117 - M118 inclusive. I think that's what >> you're asking for - please let me know if I'm reading this incorrectly. >> Good luck!

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

Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> >>

with this experiment? > > On Wednesday, June 15, 2022 at 12:34:57 PM UTC+5:30 Daisuke Enomoto wrote: > >> Hello >> >> >> Apologies for the confusion

- this intent didn't show up in our review tooling (cc Jason), so it's slipped under the radar. I believe y'all have met the bar to extend again, given that the below criteria