Re: [w3ctag/design-reviews] FedCM bundle: Continuation API, account labels, custom parameters, scopes (Issue #945)

For me personally, what I'd love to hear feedback on is:
- For the [parameters API](https://github.com/fedidcg/FedCM/issues/556), how to best send the parameters to the server (see discussion in the github issue) -- prefix the builtin parameters, prefix the custom parameters, do some sort of json encoding, ...? also -- should we allow JSON for parameter values and if so how to send that to the server
- For the [fields API](https://github.com/fedidcg/FedCM/issues/559), is this the best design for this purpose? Should we try to integrate somehow with the contacts API as suggested in the issue?

IMO both of those are fairly well described in their respective explainers in the linked issue.

I'm fairly comfortable with the design of the other parts of this explainer, though if you have feedback on how we communicate back from the popup to the FedCM API in the [continuation API](https://github.com/fedidcg/FedCM/issues/555) I'd be interested in that.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/945#issuecomment-2233693524
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/945/2233693524@github.com>