Small niggle with 1Password mini & password filling using keyboard shortcut

pbryanw
pbryanw
Community Member

Hi, I'm using the Windows beta 6.0.198d.

Here are the steps to repeat the small problem I'm having:

  1. Make sure 1Password is set to start with Windows.
  2. Open a site, like the Google Accounts page (https://accounts.google.com/login), in my chosen browser.
  3. Bring up the 1Password mini window in the browser (in my case Firefox) using its keyboard shortcut.
  4. At this point 1Password mini is locked.
  5. After unlocking, it brings up a list of all my logins, not the site related ones I'm looking for.
  6. When I then click in the password field on the web-page, and launch 1Password mini with the keyboard shortcut again, this time a list of passwords related to the site are shown.

I've also noticed that this seems to be the default behaviour for other sites, on first unlocking the 1Password mini window.

I'm just wondering if the 1Password mini window could show site related passwords, when it's first unlocked on a web-page you need password filling for?

Many thanks, Paul


1Password Version: 6.0.198d
Extension Version: Not Provided
OS Version: Windows 10 x64
Sync Type: 1Password Account

Comments

  • MikeT
    edited September 2016

    Hi @pbryanw,

    Thanks for bringing this up.

    We definitely want to improve the unlocking experience to automatically show you the matching Login items list for the site you're on when you unlock 1Password mini.

    Right now, 1Password mini is not yet optimized like this, so when it unlocks, it only knows one thing, to populate the list with your database. It hasn't taken that extra step yet to go further, filtering the list to the site you're on.

  • pbryanw
    pbryanw
    Community Member

    @MikeT - Thanks for your response. I hope this is something that can be included in a future update, either during the beta process or after you release the stable version. Thanks for your help with this :+1:

  • You're welcome and yes, we do want to implement this in a future update.

This discussion has been closed.