Not sure Secure Input is being enabled when it should be
I was playing around with creating a new login, and without thinking I used my TextExpander snippet for my email address and it worked. I thought whenever I was interacting with 1Password, Secure Input was disabled. Maybe I'm wrong (it sure was convenient!) Shortly after that Secure Input did engage.
It could also be a bug in the Monterey beta too. What is beta squared?
1Password Version: 8.2.0-59.NIGHTLY
Extension Version: Not Provided
OS Version: 12.0 Beta (21A5304g)
Comments
-
Hi @nosillacast!
I thought whenever I was interacting with 1Password, Secure Input was disabled.
Only in edit mode: in other interactions with the app (such as searching, for example), TextExpander is not blocked :+1:
0 -
@ag-ana isn’t creating a new login considered editing? I was in the middle of that process.
0 -
Just tried it with espanso on - it engages secure input after a second or so from the notification I received.
0 -
Are you able to reproduce this again? I have just tried a few times even while creating a new item and snippet expansion is not working for me.
0 -
Thank you for bringing this up. We actually had a discussion about the Secure Input internally a few days ago.
One idea was to enable it for all fields in 1Password, not just the password. However, that would certainly block features like TextExpander or AutoCorrect which might be helpful when editing secure notes, etc.
0 -
@ag_ana I think I was mistaken that my TextExpander snippets were working, I think it might be the built-in Apple auto-complete that kicked in.
@roustem having TextExpander (and auto-complete) access on fields other than the password is kind of awesome, but I will leave it to the 1Password team to decide what is the right level of security!
0
