With the native password autofill enabled, Safari now prompts to store the password that was just prefilled by Dashlane.Īdmittedly, some of these issues may be Safari UX problems, HOWEVER, why did Dashlane switch to this mechanism if this was the case? Safari native autofill requires fingerprint or other authentication every time, slowing the process down.ĢFA tokens are not autofilling when Dashlane has been set up as the authenticator.ĭisabling the extension means no access to payment information or notes – and they removed the desktop app some time ago in favour of the extension, which they are now recommending not to use in Safari? This does not make sense to me. It isn't picking the right password for the correct subdomains (I use a domain with many subdomains, each with different accounts - worked perfectly before) and doesn't show the name of the account in the Safari picker, making it different to choose the correct one without going into the extension itself.
I opened Safari this AM to be prompted by Dashlane that the autofill mechanism had been changed – I followed the help article ( ) and have enabled the native Safari autofill, HOWEVER, this has several major drawbacks: Have been a Dashlane customer for probably six years, but for some reason, for the last few years, they have embarked on a mission to slowly erode the user experience.
0 kommentar(er)
