- From: David Waite via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Sep 2023 15:47:32 +0000
- To: public-webauthn@w3.org
> I fully agree with Adrian here. Intercepting the native UI seems like a terrible idea. > > I'm hoping that it's just a temporary solution until there's a way to configure passkey providers on the system level on all platforms (similar to iOS 17). Every .create() and .get() should invoke the native platform WebAuthn UI and only the way the passkey is stored and synced changes. There are complex user-expectation and market challenges here. I would personally recommend further discussion to be on a more-related issue, preferably not one which is closed. This issue dealt with use of WebAuthn to enable functionality within a web extension, which do not have a stable origin (and thus a stable RPID) across web extension implementations in various browsers. It does not deal with web extensions offering credential functionality to web applications via patching or other API. Proposal of new web extension API, such as a way to offer credentials to the browser/platform UX without page modifications, would likely need to be within the WebExtensions CG - I believe WebAuthn WG is currently only chartered for web apps. -- GitHub Notification of comment by dwaite Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1766#issuecomment-1729849540 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 September 2023 15:47:34 UTC