Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
#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 put, I prefer the browser extension to select credentials for logging in. It handles OTP codes faster and easier than the system autofill in iOS/iPadOS. Instead, using the system autofill requires extra taps, needlessly populates the clipboard with OTP codes, and generates notifications about the OTP being copied to the clipboard that I'm frequently needing to dismiss.
I'm not sure if this is something that can be made optional in the browser extension settings, but I strongly dislike this new behavior and hope that it will be reverted to the previous behavior, or at least made optional.
Thank you.
59 Replies
Given the decision to effectively disable the 1Password extension when using native iOS/iPadOS autofill, how we go about creating Masked Emails through Fastmail now?
- 1P_Dave
Moderator
The native iOS AutoFill experience currently doesn’t support Fastmail masked email addresses. For now, if you're using iOS AutoFill, the best option on iOS is to use the Fastmail app to manually create masked email addresses. That said, I’ve shared your feedback with our team internally!
-Dave
I experiencing much of the same issues as mentioned by others above. This very much feels like “cart before the horse”.
The experience is especially worse on iPadOS where using the extension along with Safari meant that I didn’t have to reach for my laptop every time I needed to do something.
I'm sorry but this really is huge UX setback. Now it's practically impossible to use passkeys and Safari extension. To use passkeys "AutoFill from" 1Password has to be enabled but this disables extension's autocomplete feature.
This is not a solution if you have multiple accounts for one domain, which is a situation I deal with dozens of times per day.
Previous flow:
- Open page
- Tap correct login from inline extension
New flow
- Open page
- Dismiss autofill suggestion
- Tap key icon
- Look at list of about a dozen logins, which are titled by their username, not their title like in 1Password, so I have no idea which one I need
- Tap the 1Password icon
- Authenticate
- Tap the login I need
- Tap the login button
It is torturous.
Came here to concur that this new experience is terrible. I cannot state enough how much of a differentiator (read: advantage) the Safari extension has been for 1Password vs. other password managers for me, ever since its launch several years ago. Or let me put it this way: you built an experience that has made me never want to go back to the old way of doing things, let me use it for years, and ripped it away with this update. The whole “you can use it if you disable systemwide autofill” argument is frankly ridiculous, and I consider that to essentially be “we’re taking away the Safari extension” because systemwide autofill is nonnegotiable. All of this could have been avoided with even a toggle, and I beg 1Password to reconsider forcing this on me. 1Password just got considerably more expensive, and taking away a massive reason it was better than other password managers does not sit well with me.
- 1P_Dave
Thanks for your feedback. I’ve shared a more detailed explanation in my pinned post, but in short, we had to disable the browser extension’s inline menu because it was conflicting with iOS AutoFill when enabled. Our team will continue exploring better solutions for the future.
-Dave
I agree, the new experience is terrible. I’ve also experienced the “save” prompts when the password hasn’t changed. Other issues include:
- being forced to save a new item when I reset passwords, rather than update existing
- after I fix the above and delete the duplicate, then try to login with the new password, it still shows the new entry that’s already deleted. And if I autofill with the corrected entry, it fills the old password instead.
- overall, the iOS autofill experience is clunky. Having to have it take over the entire screen to unlock is super annoying. Especially with so many sites that separate out entering username and password, so you have to do it at least twice. The inline is so much smoother.
if you can work out these glitches and potentially work with Apple to improve the overall autofill experience, I’m all for it. But until then, please make this optional.
- 1P_Dave
I apologize for the delayed reply. Thank you for the feedback and I'm sorry that you're running into autofill issues. You wrote:
after I fix the above and delete the duplicate, then try to login with the new password, it still shows the new entry that’s already deleted. And if I autofill with the corrected entry, it fills the old password instead.
That doesn't sound right. Would you mind reproducing the issue again using the latest version of 1Password and then I'd like to ask you to create and share a 1Password diagnostics report from your iOS device:
Send a diagnostics report (iOS)
Attach the diagnostics to an email message addressed to support@1password.com
With your email please include:
- A link to this thread: https://www.1password.community/discussions/1password/me-271-feedback-inline-menu-hidden-in-safari/168853
- Your forum username: bkrodgers
You should receive an automated reply with a Support ID number. Please post that number here. Thanks very much!-Dave
Thanks Dave. I sent it over, ticket 569830. It's easily reproducible for me when trying to update my password for this very site. In fact, when I reported it, it was because I was resetting my password so I could come here to share my opinions on this release. The resulting experience only underlined how broken this version is.
- 1P_Dave
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 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.
That being said, our team is actively evaluating the situation and keeping an eye on everyone's feedback in order to determine the best path forward. Your experience will help shape how we move forward. We appreciate you taking the time to share it.
-Dave
- 1P_Dave
Marking a post as the solution in a thread doesn’t necessarily mean the issue or request is fully resolved or closed. It’s simply a way to surface the most current and helpful answer for anyone who comes across the thread later.
Your feedback is being heard. That said, until our developers are able to address some of the conflicts between 1Password for Safari and native AutoFill, there isn’t much new to share at the moment.
-Dave
Hi 1P_Dave, could you kindly provide a status update on this issue, and reopen the thread? As you can see there are dozens of users coming out of the woodwork and signing up for the forums just to restate how hard it is to use 1Password after the recent changes—we would really appreciate an update and indication that the 1P team is aware of this and planning to fix or roll back…
- 1P_Dave
The thread remains open, and our development team actively reviews all feedback. We’ve pinned the post above so new readers can quickly get up to speed without having to scroll through the full discussion.
In Safari on iOS, the suggestions menu is currently disabled when system AutoFill is enabled due to unresolvable conflicts between the two features. We’ve reported this to Apple and will continue exploring ways to restore the previous behaviour if a reliable solution becomes available.
I'm sorry again for the change in how you use 1Password in Safari on iOS. We'll continue to work to improve the experience and we appreciate all of the feedback from everyone.
-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
