Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
Solved
#ME-271 feedback: Inline menu hidden in Safari on iOS when system AutoFill is enabled
Hello,
I recently noticed that a lot of login forms were no longer showing the 1Password drop-down to select a credential. I believe it is related to this change referenced in the title.
Simply p...
Hello 1bvr! 👋
Thank you for reaching out about this! When 1Password is set as your system autofill provider on iOS, the inline menu in the Safari extension is now hidden to prevent conflicts between the two filling experiences.
iOS 26 introduced enhancements to AutoFill, including support for strong password generation. This allows 1Password to integrate more deeply with iOS, enabling features like creating strong passwords and filling or saving login credentials directly through AutoFill on your iPhone and iPad.
At the same time, we’ve encountered some unavoidable conflicts between iOS AutoFill and the browser extension that don’t currently have a technical solution. We’re working closely with Apple to explore ways to resolve these issues in the future. In the meantime, we’re focusing on making native AutoFill on iOS the primary way to fill, while the Safari extension continues to provide additional capabilities beyond it.
Your feedback will help shape how we move forward. We appreciate you taking the time to share it.
-Dave
1P_Dave
Moderator
ModeratorHello 1bvr! 👋
Thank you for reaching out about this! When 1Password is set as your system autofill provider on iOS, the inline menu in the Safari extension is now hidden to prevent conflicts between the two filling experiences.
iOS 26 introduced enhancements to AutoFill, including support for strong password generation. This allows 1Password to integrate more deeply with iOS, enabling features like creating strong passwords and filling or saving login credentials directly through AutoFill on your iPhone and iPad.
At the same time, we’ve encountered some unavoidable conflicts between iOS AutoFill and the browser extension that don’t currently have a technical solution. We’re working closely with Apple to explore ways to resolve these issues in the future. In the meantime, we’re focusing on making native AutoFill on iOS the primary way to fill, while the Safari extension continues to provide additional capabilities beyond it.
Your feedback will help shape how we move forward. We appreciate you taking the time to share it.
-Dave
Well...that would have been good to be proactively communicated! I've run into the same issue also with the save password stuff down in the thread.
Why are such changes not communicated?
- 1P_Dave
You can find the change mentioned in our release notes, which are published to both the App Store and our website.
That being said, I'll share your feedback with the team so that we can explore other ways to notify folks about changes like this in the future. Thank you for the feedback!
-Dave
You mean:
- We’ve made improvements to how 1Password interacts in form fields in the upcoming releases of Safari.
Now that this has been released publicly and I've encountered it, I have to add my voice to the chorus stating this change is awful, for reasons I pointed out in support ticket 563436.
And the official stance can't be that we can either have a good autofill experience in Safari, or autofill everywhere else in iOS, but not both? That's absurd.
Hi Dave,
Thanks for responding to my feedback. That is disappointing news to hear, for the reasons I mentioned previously.
I also noticed that since this change, nearly every credential that is autofilled by the native autofill in Safari generates a prompt asking me to save the password even though the password is already saved. If I tap "Save," it then offers to "update" the credential in 1Password. But the password being saved is the same password that 1Password just autofilled through the native autofill.
- 1P_Dave
Thank you for reporting this! Our team is working on improvements to avoid the "Save Password" prompt from appearing, those improvements should be released within the next few updates.
-Dave
!36582
I just found this thread. Is this a joke? Like literally everyone else, here, I thought my extension was broken. What a moronic decision.
