Forum Discussion

1bvr's avatar
1bvr
Occasional Contributor
1 month ago

#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...
betas
browser extension
discussion
ios
WorldIRC's avatar
WorldIRC
Dedicated Contributor
25 days ago

The regression in functionality is driving me nuts.  The only reason I use 1Password vs. the alternatives is due to Inline functionality within Safari for iOS.  

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    23 days ago

    WorldIRC​ 

    I'm sorry for the change in how you use 1Password in Safari on iOS. Our development team will continue exploring ways to restore the previous behaviour if a reliable solution becomes available. 

    -Dave

    • WorldIRC's avatar
      WorldIRC
      Dedicated Contributor
      23 days ago

      Dave, can your development team not revert back to "the conflict"? It's not like the app was unusable and the consensus here was the experience with "the conflict" is better than where we are left now.

      Or...add a toggle in to optionally re-enable the in-line understanding the conflict. 

      • 1P_Dave's avatar
        1P_Dave
        Icon for Moderator rankModerator
        20 days ago

        WorldIRC​ and Sir0bin​ 

        I'm happy to share additional details. As we've expanded support for new iOS 26 APIs that enable features like autosave and strong password generation, we uncovered an unavoidable conflict: iOS can no longer distinguish between a password filled by the 1Password browser extension and one typed in manually. That misinterpretation causes iOS to prompt you to save or update credentials you just filled, as if you had typed them manually, creating a confusing loop.

        To answer why this wasn't an issue that you've run into before: it's because support for these APIs is new in recent versions of both iOS 26 and 1Password. On these latest versions, in our internal testing before public release, the browser extension and native AutoFill began interfering with each other in a way that required us to disable the inline menu as a mitigation for folks who had both 1Password for Safari and native AutoFill enabled on the same iPhone or iPad. 

        The change wasn’t made lightly. We concluded that iOS prompting users to save or update a login after autofill would degrade the experience more than disabling the inline menu and relying on native AutoFill for usernames and passwords. We're currently exploring the best path forward and keeping an eye on everyone's feedback.

        -Dave