Ctrl \ not autofilling logins

cbb
cbb
Community Member
edited April 2023 in 1Password 7 for Windows

I navigate to a page with a login. Press Ctrl \ . 1password mini pops up with the correct login, but it doesn't automatically fill it in. To fill the login I have to click on it in 1password mini. This behaviour changed about 3 betas ago, before that Ctrl \ would autofill without the extra click. This is the same in Firefox and Chrome and on all sites with saved logins.

Is this intentional? I don't think it is as you still refer to Ctrl \ autofilling in several places.


1Password Version: 6.5.400
Extension Version: 4.6.4.b3 (Firefox)
OS Version: Windows 10
Sync Type: 1password account

Comments

  • Hi @cbb,

    Thanks for writing in.

    No, it is not intentional. Did you report this before? I don't see any other comments or email from you about the issue three beta updates ago.

    I think I know what might be the issue. Click on 1Password mini in your browser and click on the Vault Selector on top left, select All Vaults and now try again, does 1Password fill without bringing up 1Password mini?

  • cbb
    cbb
    Community Member
    edited April 2017

    Thanks for your quick reply. No I didn't report it before but mentioning vaults made me realise what was causing it. I was using 1password alongside Roboform to start with and as I logged in with Roboform I was saving each login to 1Password. When my free trial expired and I decided to pay for 1Password I was left still left with several hundred logins in Roboform that weren't yet in 1Password. Most of them probably aren't valid any more, but I didn't want to lose them so I exported everything to a CSV file and then imported into an Archive vault in 1Password, so my most used logins now have duplicates in the Archive vault. If I delete the duplicates everything works fine.

  • Hi @cbb,

    Thanks for writing back to let us know that. We do have a bug where Ctrl + \ doesn't work if you're in a specific vault instead of All Vaults. We will fix this soon.

This discussion has been closed.