Re: [w3ctag/design-reviews] FedCM: Alternative Fields in Account Selection (Issue #1074)

jyasskin left a comment (w3ctag/design-reviews#1074)

Thank you for sending us this question! We think the overall capability makes sense, and we're glad to see it proceeding through the FedID WG.

On the naming question, we think it's important that FedCM pick one of the existing sets of names, and re-use those names instead of inventing its own. (Even if both existing options for a name are objectively bad in certain ways.) Because there's a proposal to use FedCM fields to populate form autofill (https://github.com/w3c-fedid/FedCM/issues/694), we're inclined toward matching the [HTML autocomplete names](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill-field).

We also note that the `tel` autocomplete field describes a canonical format of "ASCII digits and U+0020 SPACE characters, prefixed by a U+002B PLUS SIGN character (+)" (e.g. "+1 617 253 5702"), while the OIDC `phone_number` field recommends to use the [E.164](https://www.itu.int/rec/T-REC-E.164-201011-I/en) format (e.g. "+1 (425) 555-1212"). Your eventual spec should say what's expected and whether and how UAs are supposed to convert them.

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

Message ID: <w3ctag/design-reviews/issues/1074/2815652797@github.com>