LGTM to experiment 147 to 152, inclusive > > This is a long-awaited feature, and it was thoroughly discussed in the > WebPerfWG > > On Wed, Mar 18, 2026 at 12:14 PM Chromestatus

is this intent asking for an extension to the previous 144 end >>>> date? >>>> >>>> Best, >>>> >>>> Alex >>

>> Intent-to-Ship (I2S). I definitely share the goal of filing it soon. >> >> However, since the primary purpose of this extension was to secure the >> crucial

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 145-147 inclusive. >>>>>> >>>>>> On Fri, Dec 19, 2025 at 2:52 PM Reilly Grant >>>>>> wrote: >>

LGTM to experiment from M141 to M147 inclusive. > > On 8/13/25 4:40 pm, 'Thomas Lively' via blink-dev wrote: >> Good question! The first toolchain to support

Thanks, Noam. LGTM1. On Monday, March 9, 2026 at 12:03:32 PM UTC-7 Noam Rosenthal wrote: > > > On Mon, Mar 9, 2026, 6:53 PM Alex Russell >

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

LGTM to experiment from M146 to M151 inclusive. On 3/5/26 8:37 pm, Huanpo Lin wrote: > Not quite sure about why the system is not including Goals for > experimentation correctly

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

run the experiment (I am supportive too, > FWIW), but one question below: > > Technically, niche issues remain where in serialization, with the new Rust > parser we may

from this intent. >> >> Best, >> >> Alex >> >> On Wednesday, January 28, 2026 at 10:05:36 AM UTC-8 Chris Thompson wrote: >> >>>

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

of the experiment. thanks, Mike On 1/29/26 11:57 am, Garrett Johnson wrote: > Was this extended beyond Chrome 141, or was that the end of the > experimental labels? > Thanks

LGTM to experiment from M145 to M150 inclusive. On 1/21/26 4:04 pm, Michael Wilson wrote: > *Contact emails* > hongchan@chromium.org, mjwilson@chromium.org > > *Specification

LGTM to experiment M144-M149 inclusive (6 milestones, rather than the requested 7) Please change the chrome status entry to indicate the above. On Tuesday, January 13, 2026 at 7:28

LGTM to experiment an additional 3 milestones from M145 to M147 inclusive. On 1/8/26 9:30 pm, Yoshisato Yanagisawa wrote: > Thank you for the question. Here is what we've learned

LGTM to experiment M144-M148 inclusive On Wednesday, December 17, 2025 at 6:57:15 PM UTC+1 Minh Le wrote: > Dear Blink-dev owners, > > I added "Experiment goals"

more developers experiment with this API. >>> >>> WebView application risks >>> >>> Does this intent deprecate or change behavior of existing

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

discuss this intent. LGTM to extend to M146, contingent on the fact that we set up a renewal flow that only allows renewals for existing participants. However, Camille will be out for

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

LGTM to experiment from 143 to 148 inclusive. On 11/4/25 1:37 pm, 'Lia Hiscock' via blink-dev wrote: > We're requesting m143 to m148 inclusive. > > Thanks! >

review the Intent to Extend Experimentation >> for the Writer API. Let me know if you have any questions. >> >> Thanks, >> Deepti >> >> >>

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

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

proposal in Intent to Experiment: >> TCP Socket Pool per-Top-Level-Site >> . >> Unlike that proposal, this one uses randomization to mitigate attacks >>

support this intent. >>> >>> Stephen. >>> >>> On Thu, Oct 9, 2025 at 11:45 AM Ari Chivukula >>> wrote: >>> >>>

extend the experiment to 145 inclusive On Wednesday, October 8, 2025 at 11:25:22 AM UTC-4 Vladimir Levin wrote: > LGTM > > On Wednesday, October 8, 2025 at 11:14:48 AM UTC-

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