Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Can’t close “save login” popup
I log in to my bank with a PIN. When 1P is not unlocked, it pops up a message saying “Save login,” prompting me to unlock 1P.
No matter how many times I click the “X,” the popup will not close until I refresh the page.
1Password for Mac 8.11.16
macOS 12.7.6
1Password for Safari 8.11.16.35
(Why did you get rid of the version number fields?)
5 Replies
- 1P_Dave
Moderator
Hello! 👋
I'm sorry for the delay in replying. Are you still running into the same issue when using 1Password 8.11.20? If you are then can you share the website where you're seeing the issue? Or does it occur on every website?
Why did you get rid of the version number fields?
Can you clarify which "version number fields" you're referring to? If you can provide a screenshot then that would help me understand what's changed.
I look forward to hearing from you.
-Dave
Yes, it’s still happening consistently in 1Password for Mac 8.11.22 (81122027), Safari extension 8.11.22.27, macOS 12.7.6, Safari 17.6. And yes, on every website. It’s quite frustrating, as the only way to get rid of it and see what’s behind it is to reload the page—which, in the exact situations it’s most likely to be up, often results in losing data (shopping cart info, etc.). I’m also noticing it on Safari for iPadOS 17.7.10, 1Password for iPadOS 8.11.22.
And—sorry—the “version number fields” I’m referring to are the ones here in the forums.
- 1P_Dave
I'm sorry for the delay in replying. I've tried to reproduce the issue on autofill.me (our testing website) but I'm not seeing the same behaviour when using 1Password for Safari 8.11.27.2. After the "Save Login" notification appears, I click X and the notification is dismissed. However, I don't have access to an older device running macOS 12.7.6 or iPadOS 17.7.10.
I've checked with my colleagues and it appears that we did receive reports of various symptoms (including a non-dismissable prompt from some users) with Safari 17.6 and Safari 18.5. The issue was reported to Apple and a fix was made available in Safari 18.6 which is available in macOS 15.6 and iOS 18.6.
If possible, I recommend that you upgrade to a version of Safari that includes the fix. If you're unable to upgrade your device then using a different browser that doesn't have the same issue (like Chrome) is the best workaround.
And—sorry—the “version number fields” I’m referring to are the ones here in the forums.
Thanks for clarifying. Last year, we transitioned to a new community platform which doesn't include fields for version numbers. I'll let the community administration team know that this is something that you'd like to see come back if possible.
-Dave
