trial or experiment for a feature may only run for 6 milestones" without knowing my initial ask was for just 3 milestones. I apologize for that and am going to seek updating internal

standard > experiment. Does this extension also require 3? > > Thanks again! > > On Thu, Jun 6, 2024 at 1:00 AM Mike Taylor wrote: > >> LGTM to extend one more

to previous Intent discussions >>> >>> https://groups.google.com/a/chromium.org/g/blink-dev/c/W8j6RKDeRoM/m/FyCKOAG9AAAJ >>> >>

and the intent to launch > will be submitted within the next 1-3 milestones). > > > On Tuesday, June 25, 2024 at 7:48:07 PM UTC+2 Daniel Bratell wrote: > >> Any reason

LGTM to experiment for 3 more milestones. Also: I asked Francis offline about the "soft launch in 126", and he clarified that it means we currently support both the new and

LGTM to experiment for 6 milestones from M128 to M133 inclusive. >> On 6/22/24 1:44 PM, Rick Byers wrote: >> >> Hello blink-dev, >> I'd like to request

want the experiment to run? > > On Tue, Jun 11, 2024 at 9:02 PM 'Alan Baker' via blink-dev < > blink-dev@chromium.org> wrote: > >> Contact emailsalanbaker

continue the experiment after Chrome 127, you'll need to register for a new token (CompressionDictionaryTransport*V3*). There were changes since the first trial. So please

126 (Intent to Ship thread > ) > and the flag has been enabled in the 126 branch. > > However, we have noticed an issue with the origin trial system which will > create a significant

LGTM to experiment from 127 to 133 inclusive >> >> On Tue, May 28, 2024 at 12:54 PM Di Zhang wrote: >> >>> Thanks Mike. Your explanation makes sense and we

to "Intent to ship: Skip Ad in Picture-in-Picture window" > > If you have any further questions or concerns, please let us know. > > Thanks, > Jiaming >

of renewed experiment). This ensures that partners have time to mint a new token and roll it out to their production enviornment ahead of m127 shipping to Stable. On Wednesday, May 15

LGTM to experiment % requesting the Security, Privacy, Debuggability bits. On 5/16/24 1:28 PM, Mike Taylor wrote: > > Thanks - LGTM to experiment from M126 to M131 inclusive

do the experiment on milestones 128 - 132. > > On Tuesday, April 23, 2024 at 4:01:15 PM UTC-4 Nicolás Peña Moreno wrote: > > I sent this intent before the feature was ready

This intent is also missing the normal info we have in I2Es, but I found https://chromestatus.com/feature/5133113939722240. LGTM to experiment from M127 to M130 inclusive. On 5

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 >

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: > >>

>> 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