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

LGTM to experiment M150-M153 inclusive (but please merge the explainers >>>> to avoid confusion :D) >>>> >>> >>> Thanks for the quick

. This experiment will provide valuable validation >> in real-world use scenarios, and should help us gauge the >> proposed API's fitness, ergonomics, and performance

LGTM to experiment M150-M155 On Tue, May 19, 2026 at 11:31 AM Yoav Weiss (@Shopify) < yoavweiss@chromium.org> wrote: > > > On Tuesday, May 19, 2026 at 5:26:35 PM UTC

LGTM to experiment from M149 to M156 inclusive. (Note: this looks like longer than usual, but we're switching to two week releases in the middle - so it's still under the permitted

LGTM to experiment 145-147 inclusive. >>>>>>>>> >>>>>>>>> On Fri, Dec 19, 2025 at 2:52 PM Reilly Grant >>>

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

LGTM to experiment from M148 to M153 inclusive. On 4/1/26 3:41 pm, Deepti Bogadi wrote: Contact emails mem...@google.com, dbo...@google.com, m...@google.com Explainer https

of user intent. By embedding a > browser-controlled element in the page, the user's click provides a clear, > intentional signal. This enables a much better prompt UX and

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

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

Your current experiment is approved up to and including milestone > 150 (branching in a month or two). You mentioned 151 in your post. > Is it correct that you are requesting a single

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

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

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

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