- From: Emil Lundberg via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Sep 2024 08:51:32 +0000
- To: public-webauthn@w3.org
>This proposes a new field be added to [PublicKeyCredentialRequestOptions](https://www.w3.org/TR/webauthn-3/#dictdef-publickeycredentialcreationoptions). The field is called display, and initially has two values: autofill and ambient. When unspecified, its default value is used, which is autofill. > >Setting the display field in a request that does not specify conditional mediation results in an error. Related to @MasterKale's comment: I agree this seems like this would be better expressed as new `mediation` option value that is mutually exclusive with `mediation: "conditional"`. For example, `mediation: "ambient"`. Since `mediation: undefined, display: "ambient"` is an error, the API would be better if that combination is impossible in the first place. Would that work? One possible issue could be that this might interfere with the last paragraph: >If the site wants to have the Ambient UI prompt and also has a sign-in form on that page, the autofill behavior still works. That is, on a request with display: ‘ambient’ if the user dismisses or ignores that UI but then clicks on a webauthn-tagged input field, the autofill UI will show the same as for a display: ‘autofill’ request. But maybe that could be addressed by calling the option value something like `mediation: "conditional-ambient"`, to make it clearer that this is an "extension" of conditional medation? -- GitHub Notification of comment by emlun Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2144#issuecomment-2343040581 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 September 2024 08:51:33 UTC