User-agents may make some reasonable filtering options on behalf of the users, however, the specification should call out behaviors that could deny users choice. For example, if a user has isLoggedIn at two IdPs and one has higher latency in response than the other, the user should know they have the option to wait for one of the IdPs. If one of the IsLoggedIn IdPs returns accounts and the other does not, the user should still have the option to select one of those and establish an account. Finally, even if a user does not have IsLoggedIn set for an offered IdP, that may be their preferred IdP for the resource; hiding that option may deny the user access to the resource.
The spec must confirm that if the user islogged in to multiple IdPs the RP has called FedCM with.. all IdPs MUST be shown
The spec must confirm that that even if the isLogged in multiple, even those IdPs that return 0 accounts MUST be shown
--is another multiple IdP issue the Order? That clients can choose to show isloggedin with accounts more prominently than isloggedin with no accounts , but otherwise the list should be in the order specified by the OP?