LGTM to experiment M148-M150 inclusive. Thanks for working on this and for making progress on WPTs. If more extensions will be needed in the future, the API owners would expect to see

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 ship a new API.

LGTM to experiment from M148 to M151 inclusive. > On 4/9/26 2:49 pm, Philip Rogers wrote: > > *Contact emails* > chri...@chromium.org, schenney...@chromium.org, pdr

LGTM to experiment from M148 to M150 inclusive. On 4/8/26 7:23 pm, Chromestatus wrote: > *Contact emails* > ekaramad@chromium.org, iclelland@chromium.org, mustaq@chromium

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 M148 to M153 inclusive. On 4/1/26 3:41 pm, Deepti Bogadi wrote: > > Contact emails > > memmott@google.com, dbogadi@google.com, msw@google.

LGTM to experiment M148-M150 inclusive On Wednesday, April 1, 2026 at 5:17:45 PM UTC+2 Noam Rosenthal wrote: > On Wed, Apr 1, 2026 at 3:55 PM Daniel Bratell wrote: > >> Has

Subject: Intent to Experiment: Container Timing Contact emailsjwilliams720@bloomberg.net Explainerhttps://github.com/WICG/container-timing Specification https://

LGTM to experiment On Mon, Mar 30, 2026 at 4:33 PM Chromestatus < admin@cr-status.appspotmail.com> wrote: > *Contact emails* > kschmi@microsoft.com > > *Explainer

LGTM to experiment M148-M153 incusive On Thursday, March 26, 2026 at 12:47:06 AM UTC+1 liahi...@microsoft.com wrote: > *Contact emails* > > liahiscock@microsoft.com

to previous Intent discussions > > Intent to Prototype: > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68b670ba.050a0220.270bc4.0593.GAE%40google

to > experiment 145-147 inclusive. > > On Fri, Dec 19, 2025 at 2:52 PM Reilly > Grant wrote: > > On Friday, December 19, 2025 at > 11:50:19 AM UTC-8 Chromestatus

proposal to experiment with a set of FedCM >> extensions to provide a structured tool to allow agentic >> browsers to log users in to websites safely using their >>

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

willing to experiment so 3 milestones might be a bit short. Either way, you have the required lgtm so good luck! It seems like a useful API. And you can request an extension if it's

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

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

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