Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Thanks Chris and Rick for the clarifications. I'm happy to approve an extension given that partners are actively experimenting. LGTM to extend to M130 or 131 inclusive - whichever is more useful (either way, you're still within the default 6 milestone limit for experiments). On 9/12/24 6:49

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Thanks for your response Mike; I do appreciate that OTs shouldn't be used as soft launches, and it's nice to hear that TAG reviews technically aren't blocking. Rick, thanks for providing that context. You are absolutely correct; that partner is still running an experiment and may have feedback

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

On Wed, Sep 11, 2024 at 3:04 PM Mike Taylor wrote: > Hey Chris, > > A few thoughts: > > We do not block shipping features if TAG is slow with their responses. But > that said, I see the TAG review was requested just 20 hours ago - we do > like to give them a reasonable amount of time to respond (

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Hey Chris, A few thoughts: We do not block shipping features if TAG is slow with their responses. But that said, I see the TAG review was requested just 20 hours ago - we do like to give them a reasonable amount of time to respond (this is usually on the order of a few weeks, maybe longer if

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

It's not exactly for experimentation, technically. My understanding is that we need to have a verdict from the TAG review before we send an I2S, but I don't think it's realistic to expect one before M130 branch cut (9/16/23). (I also need to go through I2S pre-review and launch bug approval befo

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Hi Chris, Sounds like good progress, thanks. Could you also tell us the reasons you need to continue experimenting? On Wed, Sep 11, 2024 at 6:43 AM Chris Fredrickson wrote: > Hello again - we'd like to request another OT extension, through M130 > inclusive. As a demonstration of progress, we ha

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Hello again - we'd like to request another OT extension, through M130 inclusive. As a demonstration of progress, we have: - Opened a spec PR - Requested formal position signals from Firefox

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

On 7/24/24 8:06 PM, Chris Fredrickson wrote: My apologies, I misunderstood the process here. I hereby formally request an extension for this OT, through M129 :) Thanks, I formally LGTM the request to M129 inclusive. :) Re: the OT dashboard, I've already requested an OT extension through the ch

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Hi Mike, My apologies, I misunderstood the process here. I hereby formally request an extension for this OT, through M129 :) Re: the OT dashboard, I've already requested an OT extension through the chromestatus entry; I believe the OT dashboard will be updated to reflect that once the OT team

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Hey Chris, Per the process, you'll need to formally request an extension, rather than treat this as an FYI. (Also, I just double checked and https://developer.chrome.com/origintrials/#/register_trial/4008766618313162753 is only available until M127. Note there's a 2 month "grace period" whe

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

FYI, we're going to extend this OT another 2 milestones, to 129 inclusive. (Existing OT tokens will still work, they won't expire IIUC.) On Tuesday, May 7, 2024 at 11:02:03 AM UTC-4 Mike Taylor wrote: > LGTM to experiment from 126 to 127 inclusive. > On 5/7/24 10:52 AM, Chris Fredrickson wrote:

Re: [blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

LGTM to experiment from 126 to 127 inclusive. On 5/7/24 10:52 AM, Chris Fredrickson wrote: Contact emails johann...@chromium.org, cfred...@chromium.org, y...@chromium.org Explainer https://github.com/explainers-by-googlers/storage-access-for-fedcm

[blink-dev] Intent to Experiment: FedCM as a trust signal for the Storage Access API

Contact emails johann...@chromium.org, cfred...@chromium.org, y...@chromium.org Explainer https://github.com/explainers-by-googlers/storage-access-for-fedcm Specification None (TBD) Summary Reconciles the FedCM and Storage Access APIs by making a prior FedCM grant a valid reason to automa