Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
samdale67
11 months agoNew Contributor
Don't Remember Last Search
For my workflow, I always get frustrated when I return to 1Password and find that my previous search is there. I usually want to start a new search when I activate 1Password. Is there a way to turn o...
scott2023
9 months agoOccasional Contributor
1P_Davesamdale67Hi! I'm jumping in to the conversation here because I have the same issue and find it soooo annoying. :) (I logged this as an issue on the old forums, and was told a fix was in process.)
I use command-F to start a new find. My personal expectation is that command-F will:
- move focus/cursor to the search box at top
- empty the search box
- let me start typing a completely fresh search
My expectation is that way because that's how almost every other software UI I use works.
I think the current UI in 1Password is confusing because:
- after doing a search, the search results (rightly) persist, and
- the purple bar beneath the search box (rightly) displays the search criteria, which (rightly) explains the results you see directly below that, but
- the search box itself is emptied out and reads "Search in VAULT NAME"
This creates a conflict of expectations because the search box (empty!) does not agree with the purple results definition.
It's even more confusing because then clicking back into the (empty) search box (or command-F) refills the search box with your old search terms (like `bank` in my example screenshot). Huh? This is disorienting and not expected.
For the fix, I would propose either:
- After a search, do not clear the search box contents. Keep those search terms in there, so they agree with the results below. Also, when the user hits command-F to trigger a new search, move focus to the search box and select ALL text in the box. (The net effect is that starting to type a new term will replace the current search terms.) OR:
- After a search, do clear the search box (as currently), but when the user hits command-F or clicks in the search box to trigger a new search, definitely do not refill the box with the old search terms. 😁
Thank you for reading this far and helping me process why this UI quirk bugs me so very much. 😁❤️❤️❤️
1P_Dave
Moderator
8 months agoThank you for the detailed feedback! I've shared your entire post with our Product and Development teams internally and they'll consider improvements for the future. Thank you for helping us make 1Password better.
-Dave
- reub8 months agoNew Contributor
Hi - I'm also experiencing this to great frustration. A couple comments in the hopes of constructively assisting 1Password in resolving the issue:
- I'm able to consistently reproduce this and happy to provide any diagnostics that may be of use. To be clear, this means that the previous search term is populated when I search and it is often but not always unhighlighted.
- I was surprised to read above that "When you return to the search field using Command-F, the previous search term should be highlighted. If you start typing your new search term the previous highlighted search term will disappear, giving you the same behaviour as if it has been pre-cleared." If I understand correctly, the intent here is to allow a user to search as if the prior search has been pre-cleared but also maintain the context of the prior search. I find this intended ux (as noted above by scott2023) confusing and obstructive and would argue it runs counter to well-established patterns in software search ux. Who wants to have the initial view be the last search? I would encourage 1Password to consider the wisdom of https://lawsofux.com/jakobs-law/ and reevaluate this intended behavior in favor of simply keeping the search field empty upon when a user attempts to search.