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

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 unti M133 (inclusive), which would take this OT to 6 >> milestones in total. >> >> If you'd want to extend the experiment beyond that, I'

-armed experiment to determine if it is feasible! > Awesome!! > > Thanks, > Kyra > > On Wed, Jul 3, 2024 at 10:27 PM Yoav Weiss (@Shopify) < > yoavweiss@chromium

LGTM to experiment from 131 to 136 inclusive. On 10/9/24 7:58 PM, Domenic Denicola wrote: > > > Contact emails > > domenic@chromium.org, fergal@chromium.org, kenjibaheux

LGTM to experiment, with a few notes inline. > > On Fri, Oct 4, 2024 at 5:05 AM 'Sam LeDoux' via blink-dev < > blink-dev@chromium.org> wrote: > >>

to “Intent to Experiment” blink-dev discussion >> >> https://groups.google.com/a/chromium.org/g/blink-dev/c/3escBQGtIpM/m/ntcytva5BgAJ >> >>

Reason this experiment is being extended >>>> >>>> This is needed to provide developers with enough time to pivot their >>>> drive-by web

plan to experiment with two new extensions for the Federated Credential > Management (FedCM) API: > > > - > > Button Mode API > - > > The button mode lets websites

> separate intent to extend the OT, with some details on what y'all did to push > it towards shipping > ? > > On Thu, Sep 19, 2024 at 9:28 PM Yi Gu wrote: > >>

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 user's intent. Having an in-content > element that the user uses to trigger the permission flow allows for > improved permission prompt UX for users as well as a recovery

Intent to Continue Experiment: Page Embedded Permission Control Contact emails andypaicu@google.com, pjmclachlan@google.com, engedy@google.com Explainer https://github

LGTM to experiment M127-M132 inclusive. On Thu, Jul 11, 2024 at 8:17 AM Domenic Denicola <dom...@chromium.org> wrote: Can you work on filing for TAG review, and asking other

that this experiment is going to collect data for presenting potential changes to the behaviour. That is correct, the goal of the experiment is to collect data so that we can decide whether

running an experiment and may have feedback for > us, so we'd like to not interrupt their study. (My earlier email was > definitely incorrect, I was thinking too hard about

LGTM to experiment in M128-131 inclusive. /Daniel On 2024-09-09 18:58, Victor Tan wrote: > > Hey Alex (and others), > > > Here's a few questions we asked ourselves

the updated experiment and the results are largely the same as in the first round. Caching resources corresponding to third-party opaque origin contexts results in speed-ups for

beacon-experiment@google.com > > Explainer > https://github.com/WICG/pending-beacon/blob/main/docs/fetch-later-api.md > > Specification https://whatpr

for this experiment (vs 6, which is the default allowed)? > > The sites who are interested in this are large and operate in the > financial sector, so I expect they will proceed

extend the experiment. On Fri, Aug 23, 2024 at 2:15 AM Guido Urdaneta wrote: > On Mon, Aug 19, 2024 at 3:32 AM Domenic Denicola > wrote: > >> Thanks for the responses. >

LGTM to experiment 129-134 inclusive, or shifted if you can't start in 129. That said, I would expect things to change during the experiment, including the name. Like TAG I find

block the experiment. I would suggest starting a TAG review and gathering signals from other browser vendors soon. On Wed, Aug 14, 2024 at 1:15 AM Florin Malita wrote: > The main motivation

to “Intent to Experiment” blink-dev discussion* > > https://groups.google.com/a/chromium.org/g/blink-dev/c/3escBQGtIpM/m/ntcytva5BgAJ > https://groups.google

> This intent is also missing the normal info we have in I2Es, but I found > https://chromestatus.com/feature/5133113939722240. > > LGTM to experiment from M127 to M130

LGTM to experiment M129-M134 inclusive. On Tue, Jul 30, 2024 at 9:39 PM Daseul Lee wrote: > Contact emails > > asully@chromium.org, ayui@chromium.org, christinesm@chromium