Forum Discussion

Felipe_Alvarez's avatar
Felipe_Alvarez
Occasional Contributor
4 years ago

Keyboard shortcut no longer shows me the password in clear text

Before the recent (Sept 2021) update to 1password in the browser, I used to be able to press a keyboard shortcut to reveal the password in clear text. This doesn't seem to work anymore.

It used be ALT+SHIFT or CTRL+SHIFT


1Password Version: Not Provided
Extension Version: 2.1.0
OS Version: windows 10

5 Replies

  • Felipe_Alvarez's avatar
    Felipe_Alvarez
    Occasional Contributor

    I have found a way to reproduce:

    1. windows 10
    2. vivaldi (or chromium-based browser)
    3. 1P extension 2.2.3
    4. select a Login
    5. press CTRL + SHIFT, password is revealed ✅
    6. click on the password, and choose "reveal"
    7. click a different Login
    8. press CTRL + SHIFT, password is not revealed
    9. press "copy" on a password
    10. 5. press CTRL + SHIFT, password is revealed ✅
  • Felipe_Alvarez's avatar
    Felipe_Alvarez
    Occasional Contributor

    I am on Windows 10. Clicking away from the extension always closes it.

    Ctrl + shift used to always work. Now it works intermittently. I hate saying that but it's actually true.

  • Anonymous's avatar
    Anonymous

    Hey Felipe_Alvarez! The shortcut to reveal an item's password in the extension is Control+Option. As long as the extension popup from your browser's toolbar is open, and as long as a login item is selected, that shortcut should indeed reveal the item's password. If that's not working for you, could you let me know if you're viewing your items from the extension popup? If you click away, do you close the extension popup? What specific shortcut are you using?

  • Felipe_Alvarez's avatar
    Felipe_Alvarez
    Occasional Contributor

    In 2.2.3, the keyboard shortcut works, but approx 10% of the time. When I click away, or click another Login item, shortcut does not work.

  • Anonymous's avatar
    Anonymous

    Hey Felipe_Alvarez ,
    Thanks for reporting this.

    I'll forward it to the developers for investigation (and fixing if needed).

    ref: dev/core/core#10389