- From: Rew Islam via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Apr 2025 07:13:52 +0000
- To: public-webauthn@w3.org
> I haven't checked dashlane (who are in this thread asking for a web extension API). Maybe [@irew](https://github.com/irew) can give details. - Dashlane does not invest in developing native desktop apps, the ROI is not justified for the size of our company and the limited usage of such apps by our users. In the past when we did ship native desktop apps, however our users preferred the standalone browser extension over the native app. - We will continue to monkey patch navigator.credentials.create (and get). We're only interested in `publicKey` credentials, if the RP indicates a preference for a security keys, the call is returned to the browser/OS. - There is a trend of native autofill APIs being adopted at the OS level, with support for a very limited set of data types. These are necessary on mobile, but not on desktop. We are not interested in using these desktop APIs which would limit our product features and reduce market competition. On desktop we prefer to control the UI for autofill of all types of data we support, which is much more than the OS would ever support. Even if the OS did support these types, we prefer to control the heuristics of detecting which fields to autofill, and the UI that goes with it, so we would not use the OS APIs. We consider our approach optimal for the vast majority of Dashlane users. -- GitHub Notification of comment by irew Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1976#issuecomment-2774701996 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 April 2025 07:13:53 UTC