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

for the experiment, but whenever we add >> or change or improve timing functions or functionality we need to consider >> if we have made timing attacks possible or simpler

discussed this intent at API >>> OWNERS this morning, and it isn't entirely clear why we aren't sending an >>> I2S instead. Do we not have clarity on the

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

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

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

LGTM to experiment M152-M157 inclusive. On Thursday, July 2, 2026 at 7:25:50 AM UTC-4 Yoav Weiss wrote: > *Contact emails* > yoavweiss@chromium.org > > *Explainer*

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

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 M151-M156 inclusive. On Tue, Jun 30, 2026 at 1:05 PM 'Philipp Hancke' via blink-dev < blink-dev@chromium.org> wrote: > *Contact emails* >

permission to experiment from 150 to 155. > > On Thu, Jun 25, 2026 at 1:06 AM Guido Urdaneta wrote: > >> Correction: The plan is to run the Origin Trial from 151 to 156. >

>> Intent-to-Ship, and are agreeing to treat it as such. With that >> caveat, and with the Finch rollout plan in play, LGTM1. > LGTM2 - thanks for the careful rollout

extend the experiment we think it >> would be helpful as we continue to finalize the feature. >> >> Best, >> Michael >> >> >> On Wed, Jun

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

> stable experiment) instead of just shipping > > > We'd like to get a few sites to test out the new algorithms in > real-world scenarios before shipping it, to ferret

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

dev] Intent to Experiment: Declarative CSS module scripts LGTM to experiment On Mon, Mar 30, 2026 at 4:33 PM Chromestatus <admin@cr-status.appspotmail.com> wrote: Contact

an approved intent to experiment, which you currently have > due to Mike's approval on Mar 6. In other words, you're free to experiment > up to 1% without additional approvals

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

. 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

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