in the intent. :) LGTM to extend from 136 to 138 inclusive. On 3/12/25 10:41 PM, Domenic Denicola wrote: > Hi Mike! I think we covered several of these areas in the original > post

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

to this experiment & proposal. Just yesterday, we saw YouTube add DRM to all video downloads, breaking many user's flows for the yt-dlp user-agent. At present, there's

LGTM to experiment from M135 to M139 inclusive (I think that's what you've requested, at least). On 3/10/25 7:29 PM, 'Mike Jackson' via blink-dev wrote: > Done

> the experiment, as an artifact of "progress", should they want to extend > past 135. It may be interesting to consider pausing the experiment for a > few days/

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

ran this experiment and found no significant changes for the core web > vital metrics or for the Chrome Guardrail metrics. We also conducted an > in-depth analysis of multiple

LGTM to experiment from M135 to M141 inclusive. On 2/21/25 11:23 AM, Chromestatus wrote: > > > Contact emails > > mkwst@chromium.org > > > Explainer >

want to experiment with the summarizer API On Thursday, 10 October 2024 at 09:54:21 UTC-7 Mike Taylor wrote: > LGTM to experiment from 131 to 136 inclusive. > On 10/9/24 7:58 PM

LGTM to experiment from 135 to 137 inclusive. On 2/11/25 11:22 AM, Mason Freed wrote: > > > Contact emails > > masonf@chromium.org, lwarlow@igalia.com, chromium

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

from this intent: > this is a deprecation trial for sites that might be broken by > the select parser relaxation, and would like extra time to > migrate to the new behavior. The

of an intent to ship. > > At each extension milestone, we've had high quality feedback for > performance, API usage and the security surface exposed. I'd also like

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

Reason this experiment is being extended" section. > > Kind Regards, > Andy Paicu > > > On Mon, Feb 3, 2025 at 5:35 PM Mike Taylor wrote: > > Thanks, LGTM

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

a new intent, but I don't think it'd be helpful here. LGTM to continue experimenting in M133 On Tue, Jan 14, 2025 at 7:44 PM Kyra Seevers wrote: > Hi all - Happy New Year! >

>> Goals for experimentation >> >> This experiment would allow us to receive and >> incorporate feedback on the browser's application of >>

for an experiment didn't have eyeballs on it from the > wider web standards community, it would be appropriate to request > that. But not relevant here. > >> WPT

LGTM to experiment M131-M136. On Thu, Nov 21, 2024 at 11:12 PM Shunya Shishido wrote: > Contact emails > > sisidovski@chromium.org > > Explainer > > https:/

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

the team offline to confirm that's the intent) > > On 11/18/24 5:46 PM, 'Johann Hofmann' via blink-dev wrote: >> We request to extend the origin trial to M133

LGTM to experiment M133-M135. On Wed, Nov 20, 2024 at 9:45 AM 'Daniel Clark' via blink-dev < blink-dev@chromium.org> wrote: > Done! > > > > *From:*

LGTM to experiment from 132 to 134 inclusive (let me know if I got that range wrong). On 11/15/24 6:54 AM, 'Marja Hölttä' via blink-dev wrote: > > > After getting inconsistent

extend the experiment, which currently lasts until m132 > (inclusive), to run until m135 (inclusive). > > Contact emailseladalon@chromium.org, guidou@chromium.org

LGTM to experiment M131-M136 inclusive On Tue, Nov 5, 2024 at 12:34 AM Keita Suzuki wrote: > Contact emails > > suzukikeita@chromium.org, yyanagisawa@chromium.org >

LGTM to experiment from 132 to 134 inclusive. On 10/31/24 3:56 AM, uazo wrote: > > Tracking bug > > https://g-issues.chromium.org/issues/333029146 > > Could

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

LGTM1 to experiment M132-137 (give or take an off-by-one error) > > > > On Tuesday, October 22, 2024 at 11:16:49 PM UTC-7 Domenic Denicola > wrote: > > Contact

run the experiment, but let's make sure we're open to design changes and perhaps expanding the scope to other playback types. Best, Alex On Friday, October 18, 2024 at 7:41