Re: [w3ctag/design-reviews] FedCM multi IDP support (Issue #803)

> We discussed this in our call today. It seems like a good solution from a UX perspective would be if the IDPs are loaded dynamically, but without causing layout shifts in the content of the webpage (we all hate when a button we were about to click on is suddenly displaced from under our pointer). Have you thought about making this part of the browser chrome, rather than the site? Essentially moving the rendering responsibilities from the RP to the user agent.

That is how the API works today. The current API lets the user agent take control over the UI shown for a single `get()` call. In the future, it will be possible for the RP to only invoke `get()`s and get the user agent UI 'for free'.
 
> User agents have historically had horrible UX with basic auth and certificate auth, it would be good for users if the UA could play a more active, and consitent, role in managing logged in state and UX for all forms of authentication. This implies creating other APIs beyond FedCM to handle other forms of authentication, but they could have a uniform UX. Do you think this is a direction you could see FedCM going in, in the future?

Yes, this is indeed the direction FedCM is going in. This also enables future work like reconciling different authentication choices (password/federation/passkeys) in a single user agent UI.


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

Message ID: <w3ctag/design-reviews/issues/803/1989509189@github.com>