Intent to Prototype: FedCM Navigation Interception API

[Chromestatus]

Contact emails

go...@google.com, n...@google.com, cbies...@google.com

Explainer

https://github.com/w3c-fedid/FedCM/blob/main/explorations/drafts/interception.md

Specification

No information provided

Summary

A mechanism that allows IdPs to initiate a FedCM by intercepting navigations to their URLs.

Blink component

Blink>Identity>FedCM

Web Feature ID

fedcm

Motivation

So far, we've managed to deploy FedCM on a series of deployment setups (IdPs that deploy with JS SDKs, small federations and cases where RPs can be deployed at scale), and in doing so, developed a lot of the infrastructure to meet those requirements. However, one deployment pattern (which also happens to be the most widely used) remained out of reach to deploy at scale: federation implemented with top level redirects. How can we allow an IdP to deploy FedCM without requiring their Relying Parties to change?

Initial public proposal

https://github.com/w3c-fedid/FedCM/blob/main/explorations/drafts/interception.md

Requires code in //chrome?

False

Tracking bug

https://crbug.com/455614294

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5106446501019648?gate=5110072611045376

This intent message was generated by Chrome Platform Status.