-
Notifications
You must be signed in to change notification settings - Fork 94
Status of FPWD‐identified Issues (Consensus Blockers for CR)
Heather Flanagan edited this page Aug 5, 2025
·
13 revisions
This is a tracking list of issues the WG labeled as critical open issues during the FPWD process that must be formally addressed before publication of a Candidate Recommendation.
Criteria for a feature to be in core: a second implementation that agrees with the design. All other features will be considered for an extension (which may be limited to one browser's implementation).
| Issue | Stage | Proposal | Core FedCM? |
|---|---|---|---|
| Issue 319: Allow multiple IDPs to be used | 2 | Multi-IdP API issue 5 | Yes |
| Issue 578: Allow IdPs to return JSON objects rather than Strings back to RPs | 0 | awaiting proposal | Yes |
| Issue 585: Allow IdP registration and RPs to match on a "type" – IdP Registration | 1 | IdP Registration | Yes |
| Issue 587: Why must SameSite=none? | 0 | awaiting security discussion | Yes |
| Issue 618: Support chained authentication flows before reducing heuristics and classifications/lists in navigational tracking mitigations | 0 | Yes | |
| Issue 620: Make it easier to deploy this at the eTLD+1 for registered IdPs | 1 | IdP Registration | Yes |
| Issue 729: globalObjects should be the top level window, rather than the cross site iframe when Permissions Policy is used | 0 | potential security issue? |
| Issue | Stage | Proposal | Core FedCM? |
|---|---|---|---|
| Issue 407: [Context API] - Authz / relation to ability to specify scope | 2? | proposed non-CR blocking | Yes |
| Issue 559: Allow RPs to selectively request attributes of the user’s profile | 2 | Fields API | No |
| Issue 517: Allow user agents to use "Connected Accounts Set" with flexibility | 2? | 3PC Relaxation | No |
| Issue 352: Share performance measurement with IDP | 2? | Metrics API | No |
| Issue 240: Users can’t use IdPs outside of the ones enumerated by RPs | 1 | IdP Registration API | No |
| Issue 441: The IDP has to support additional infrastructure to support FedCM | 1 | Lightweight API | No :-( |
| Issue 677 IdP Blindness: User Info VCs | 1 | Delegation-oriented FedCM | No |
| Issue 599: OAuth profile for FedCM | 0 | Not expected to be part of the spec; identifies gaps that would result in OAuth not being useful in a FedCM flow | No |
| Issue 625: Returning accounts go first in getUserInfo | 0 | No | |
| Issue 627: Add webdriver command to open PP/TOS | 0 | This will be handled in an extension | No |