Skip to main content
April 30, 2026
Question

Chrome extension login

  • April 30, 2026
  • 3 replies
  • 63 views

I find it would be helpful if after signing in with a chrome/brave browser extension, it the cursor would migrate to the search bar (Search in 1Password) at the very top of the extension. Frequently after signing on, I am looking for a site/login for something other than the page I'm currently on. 

Thanks in advance,

 

3 replies

Trevor_1P
1Password Employee
May 12, 2026

Hi @gooddog,

I've tested this on my device, and I'm seeing the search field focused after unlocking the extension so that I can immediately begin searching. Could you confirm, what version of the 1Password browser extension you have installed currently, as well as what you're seeing focused instead?

gooddogAuthor
May 12, 2026

Hi Trevor,

Thanks for reaching out, current version of : 1Password Nightly – Password Manager is Version 8.12.22.9

Should I not be using Nightly? 

Thanks in advance,

Trevor_1P
1Password Employee
May 13, 2026

Hi @gooddog,

Thank you for confirming that. I've tested this in the Nightly release as well, and am seeing the search field focused after unlocking. 

To help us further look into this, I'd like to ask you to create a short screen recording and attach it to an email to support@1password.com. Be sure not to include any private information in the recording.

With your email please include:

- A link to this thread: https://www.1password.community/discussions/1password/chrome-extension-login/169926/replies/170215

- Your forum username:

You should receive an automated reply from our BitBot assistant with a Support ID number.  Please post that number here.  Thank you!

gooddogAuthor
May 13, 2026

Trevor, thank you for the support. It looks like a windows 11, Chrome, or Brave update has solved the problem. The cursor does now appear in the search window when unlocked in the browsers. 

Thanks again,

1P_Gem
1Password Employee
May 14, 2026

Hi @gooddog, I'm glad to hear that an update seems to have resolved the issue. Thanks for letting us know!