FedCM Object Token Enhancement - #771
Conversation
|
@hlflanagan @wseltzer should we have a discussion about this proposal? Has it already happened at a meeting I missed? |
There was a problem hiding this comment.
Thanks for working on this. Added some other comments besides what Christian mentioned. I still think this needs some work, mainly in simplifying it and making it more correct to what we want.
This was last discussed here https://github.com/w3c-fedid/meetings/blob/main/2025/2025-07-29-FedCM-notes.md |
| </div> | ||
|
|
||
| <!-- ============================================================ --> | ||
| ### Token Content Privacy ### {#token-content-privacy} |
There was a problem hiding this comment.
I am not sure this section adds much value
There was a problem hiding this comment.
As I mentioned, you need to modify some other algorithms. For example, the 'show a continuation dialog' says it returns a (string, string?). And 'resolve' needs to allow passing an arbitary token too, not just a string
There was a problem hiding this comment.
Can you change resolve too? It shows as DOMString token still.
SHA: 843eb51 Reason: push, by npm1 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: 843eb51 Reason: push, by pull[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This change extends the FedCM API to allow IdPs to return structured objects directly as tokens.
Preview | Diff