Skip to main content
Calion
September 23, 2025
Solved

Safari Extension needs second click

  • September 23, 2025
  • 2 replies
  • 113 views

When 1Password is locked and I click in a login field in Safari, I can click on the lock to “Unlock 1Password.” Doing so brings up a password dialog, but nothing happens afterward until I click on the lock icon again (or exit the field and click in another). Then the list of relevant password entries pops down after a couple of seconds. If the app is already unlocked before I click in the field, then the suggestions pop-up immediately.  

macOS 12.7.6
1P 8.11.10
Safari extension 8.11.9.3  

Best answer by 1P_Dave

Hello @Calion! 👋

Thank you for reporting the issue! This is something that our development team is already tracking and hopefully will be fixed in a future update soon. While I can't say when the issue will be resolved, it'll be noted in our release notes when it is: 


Thank you for reporting the issue. 

-Dave

Issue=AUTH-140

2 replies

1P_Dave
1P_DaveAnswer
1Password Employee
September 26, 2025

Hello @Calion! 👋

Thank you for reporting the issue! This is something that our development team is already tracking and hopefully will be fixed in a future update soon. While I can't say when the issue will be resolved, it'll be noted in our release notes when it is: 


Thank you for reporting the issue. 

-Dave

Issue=AUTH-140

Calion
CalionAuthor
March 31, 2026

This is technically not fixed, as it still needs a second click, but now at least only two clicks are needed. Still, one is the correct number here.

1P_Gem
1Password Employee
April 1, 2026

Hi @Calion, thanks for the update. I'm glad to hear the behaviour has improved a little. Our development team are still looking into this one, so I've added this detail to the issue on file for them to see.

Calion
CalionAuthor
November 15, 2025

Any timeline on this? This is getting old.

1P_Dave
1Password Employee
November 17, 2025

Our developers are aware that this is something that needs to be fixed but I don't have any timelines to share. I'm sorry for the continued disruption. 

-Dave