LGTM to experiment from M139 to M144 inclusive. On 5/16/25 3:18 AM, Domenic Denicola wrote: > > > Contact emails > > ayui@chromium.org, msw@chromium.org, btriebw

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

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

when the experiment ends. > > Storage access headers make it difficult for a publisher to ascertain if > some generic third party would receive none or active on their request

run the experiment). AIUI, the design doc mentions sites attesting to > benefit from this feature, so there will be a new API involved at some > point. > > I'm happy to

during the experiment period. > > > > /Gecko/: Defer > (https://github.com/mozilla/standards-positions/issues/1067) > > /WebKit/: No signal > (https

during the experiment period. > > > > /Gecko/: Defer > (https://github.com/mozilla/standards-positions/issues/1067) > > /WebKit/: No signal > (https

LGTM to experiment from M137-M142. > > On Wed, Apr 23, 2025 at 11:13 AM 'Gabriel Brito' via blink-dev < > blin...@chromium.org> wrote: > >> Ok. Added

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

the original intent. Great > to see things evolve while in OT. > > Has there been feedback on this so far? Anything y'all can share? > > Best, > > Alex > >

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

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? > > > > Goals for experimentation

the > experiment has been expired since 134 (which is the current stable > release, with M135 scheduled to start rolling out ~tomorrow. > > If you request to extend to 136

the partner's experiment. On Thu, Mar 20, 2025 at 12:36 AM Vladimir Levin wrote: > LGTM to experiment. One of the concerns is that 2 milestones may be too > short of a duration

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

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

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