Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Native Password AutoFill Extension macOS
So one of the people in my family subscription for 1P relies heavily on iCloud Keychain. The nice piece about using the native autofill extension is entries from both show up together in-line. This h...
I've messaged 1Password support several times over the past 2+ years requesting 1Password to support MacOS native autofill as it does in iOS. Frustratingly, support just glosses over the requests for native autofill support and never actually gives a definitive answer on whether we can expect the requested feature or not.
I would really like to have the request for native MacOS autofill addressed. There are several of us who very much want it, and some, myself included, who, at this point, are debating continued support of the app based on future implementation of this. It has, after all, been available to developers for 3+ years.
Many people struggle with the competing native Mac Passkey pop-up, and the longterm 1Password Safari issue likely wouldn't have been an issue while waiting for Apple's fix had 1Password Mac supported native autofill. Even with the supposed fix, if I connect 1Password Mac to 1Password Safari, I still can't unlock 1Password form a username or password field, and, if already unlocked, I can't get the drop down to offer me any autofill suggestions.
I recently switched everything over to Apple Passwords, not because I prefer it to 1Password--I don't. However, the stability and speed of autofill is, in my experience, far better than 1Password. There's never a glitch with Passkeys, and Passwords never fails to surface logins and passwords. I understand 1Password has chosen universal autofill, but there is a decent number of users who want and have been asking for 1Password to support MacOS native autofill. Maybe give users the option if the two can't coexist.
Also, native autofill would alleviate lots of recurring problems. The long-lived problems with 1Password Safari likely wouldn't have been a problem. I'm also running the current beta for macOS Tahoe, and, similar to the issue with Safari over the past year, when I go to a website and 1Password Safari is locked, clicking the 1Password icon to unlock in the username field results in nothing: no unlocking, no TouchID prompt, and no master password prompt. I have to click the icon in the Safari toolbar, then click the TouchID icon (it should automatically offer that up), and then select autofill. I'm not interested in using universal autofill. With native integration, this would be a non-issue. I know I'm running the beta, but with a likely release in the next 2 months, I worry about another 1Passwords Safari snafu.
