Intent to Ship: FedCM: Alternative Fields in Account Selection

[Chromestatus]

Contact emails

cbies...@chromium.org

Explainer

https://github.com/w3c-fedid/FedCM/issues/435#issuecomment-2718856194

Specification

https://github.com/w3c-fedid/FedCM/pull/718

Summary

Adds support for phone numbers and usernames, in addition to or instead of a user's full name and email address as identifiers for disambiguating accounts in the account selector. Also, makes these new fields available for websites to affect the disclosure text.

Blink component

Blink>Identity>FedCM

Search tags

fedcm

TAG review

https://github.com/w3ctag/design-reviews/issues/1074

TAG review status

Pending

Risks

Interoperability and Compatibility

No compatibility risk as this only adds support for new fields Because Chrome is currently the only implementor of FedCM in general, there is no incremental interop risk for this feature.

Gecko: No signal For incremental improvements to FedCM, Firefox has asked us not to file standards position, and they will instead provide feedback in the GitHub PR. The Firefox lead engineer on FedCM has expressed support in https://github.com/w3c-fedid/FedCM/issues/435#issuecomment-2776163171

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/309) Safari has closed other position requests for FedCM subfeatures without position (e.g. https://github.com/WebKit/standards-positions/issues/120) in favor of giving a position on FedCM in general. That issue is still open.

Web developers: Positive (https://github.com/w3c-fedid/FedCM/issues/435)

Other signals:

Ergonomics

None

Activation

To fully take advantage of this feature, identity providers may have to check the browser version on the client or server side, or wait until a newer Chrome has rolled out to enough users.

Security

No security risks.

WebView application risks

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

n/a, FedCM not supported on WebView

Debuggability

Same as the existing FedCM.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No

FedCM in general is not supported on Webview. Supported on all other platforms.

Is this feature fully tested by web-platform-tests?

No

https://wpt.fyi/fedcm/alternative-identifiers Some of the UI-centric aspects of this feature can not be tested with web platform tests, but the WPT tests we added verify that phone numbers and usernames are supported as valid fields by the user agent.

Flag name on about://flags

FedCmAlternativeIdentifiers

Finch feature name

FedCmAlternativeIdentifiers

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

True

Tracking bug

https://crbug.com/382086282

Launch bug

https://launch.corp.google.com/launch/4390910

Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open source repository and its open-source dependencies to function?

No

Estimated milestones

Shipping on desktop	141
DevTrial on desktop	136
Shipping on Android	141
DevTrial on Android	136

Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

We may add support for additional fields in the future but have no concrete plans to do so. This could be things like a user's last name or physical address.

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5121180773908480?gate=5086384735649792

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67eabd7d.170a0220.8108a.08e0.GAE%40google.com

This intent message was generated by Chrome Platform Status.

[Chris Harrelson]

LGTM1

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68923f02.050a0220.1b326.0123.GAE%40google.com.

[Yoav Weiss (@Shopify)]

LGTM2

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

[Mike Taylor]

LGTM3 (and noting that the TAG review was closed as satisfied).

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b89c10e0-91b3-42b2-ad3e-c2236c9021d1n%40chromium.org.

[Christian Biesinger]

Thanks everyone for the LGTMs!

And thanks specifically to Mike for pointing that out, I have updated the chromestatus entry to indicate that the TAG is satisfied

Christian

LGTM2

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68923f02.050a0220.1b326.0123.GAE%40google.com.