Hey Alex,
You are right that they are only related in that they are extensions of the
FedCM API. We bundled them up together in the same intent since we
considered them small enough such that a single intent containing both is
still manageable, and this reduces the burocratic overhead for shipp
Thanks for the suggestion, Yoav! It seems something fetch experts have some
concerns about, so we do not plan to proceed with that suggestion at the
moment.
I'd like to append a small addition to this I2S (mainly to avoid having an
additional PSA since it is very related to this one): we would
Thanks all! This is shipping in Chrome 125.
On Wednesday, March 20, 2024 at 11:09:47 AM UTC-4 Daniel Bratell wrote:
> LGTM3
>
> I'm also a bit concerned with the risk, but it sounds like you have it
> under control and will be able to handle the rollout appropriately.
>
> /Daniel
> On 2024-03-18
I sent this intent before the feature was ready, and this required a lot of
UX work, so trial has not started. Our plan is to start on Chrome M126 so I
will assume the approvals are shifted to 126 - 130. If there are concerns
let me know, thanks!
On Tuesday, February 27, 2024 at 3:04:38 PM UTC-
We decided to further delay the start of the OT since our partner needs
more time before they can put it in front of real users, so the current
plan it to do the experiment on milestones 128 - 132.
On Tuesday, April 23, 2024 at 4:01:15 PM UTC-4 Nicolás Peña Moreno wrote:
> I sent this intent b
