Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
2 years agoBug: "Hold Ctrl+Alt to toggle revealed fields" not working consistently
In the Windows app, there is the option to Hold Ctrl+Alt to temporarily reveal hidden fields.
When starting 1Password this does not work. Toggling the checkbox off and then on again in Settings -> Security will restore correct behaviour.
1Password Version: 8.10.9
Extension Version: Not Provided
OS Version: Windows
Browser: Not Provided
9 Replies
- AliH1P
1Password Team
@IanBurnett I'm glad to hear the latest update resolved things for you.
Let us know if there's anything else we can help with!
Ali
- Former Member
Upgraded to 8.10.16 and that seems to have fixed the issue. Thanks for the update.
- 1P_Dave
Moderator
@IanBurnett, @eyetiger, @AmazingBlair
1Password version 8.10.16 now includes a fix for the issue that could prevent the “Hold key to toggle revealed fields” option from working properly after 1Password was closed and reopened.
You can find instructions on how to update here: How to keep 1Password up to date
Thank you again for reporting the issue. 🙂
-Dave
- 1P_Dave
Moderator
I'm sorry for the inconvenience. I see that my colleague has already replied to you in the other thread: https://1password.community/discussion/comment/694785/#Comment_694785
-Dave
- JamesHendersonDedicated Contributor
yep, me too (Mac). ...quite annoying.
X-link to Mac thread:
https://1password.community/discussion/142053/need-to-toggle-the-hold-option-to-toggle-revealed-fields-on-every-launch/p1?new=1 - 1P_Dave
Moderator
@AmazingBlair
I'm sorry for the inconvenience. Hopefully the issue is fixed soon.
-Dave
- Former Member
I have the same problem. I use 1Password for Windows 8.10.9 (81009046) on Windows 10. It has a workaround, but it is an annoyance. Thanks for a great product otherwise!
-Blair
- 1P_Dave
Moderator
Hello @IanBurnett and @eyetiger! đź‘‹
I'm sorry that you're having trouble revealing passwords. Our developers are already tracking the bug in an internal work item. I've added your report there and hopefully we can get this fixed soon in a future update.
As mentioned by IanBurnett, toggling the feature off and then back on will resolve the problem until the next time that you reopen the app.
-Dave
ref: dev/core/core#22935
- Former Member
I have the same problem which started with a recent update.