Chrome extension search box is not cleared when UI is closed

Ask the Community Password Manager
, ,
1

Using Chrome on macos with browser extension version
Version: 2025.5.1
SDK: ‘main (c6835e5)’
Server version: 2025.6.2
In prior versions, the search box was automatically cleared after the UI is closed.
Similar but different than an issue that was fixed in this version where the cursor/focus was not automatically set to the search box when opening the UI (that was resolved in this version). Now the cursor is in the search box, but your last search term is still there and you need to manually delete before doing your next search

Example use case:
open bw ui in chrome
search for a stored credential by typing in search box
click ‘launch website …’ button
(website opens in new tab, UI auto closes)

at this point in previous versions if I want to search for and launch another website from a stored credential I could just repeat the above steps. In this latest version, however, when I open the ui, my previous search term is still in the search box. I have to either press the escape key to clear it in one step or press the delete key many times, or select the text and press delete.

I searched for other posts regarding this topic and was surprised that I didn’t find anything because this behavior is pretty annoying - makes me wonder if this is somehow unique to my system?

2

This change was introduced with Release 2025.3.3:

2025-06-30--22-51-24-vivaldi_8RT2H4BxzB
2025-06-30--22-51-24-vivaldi_8RT2H4BxzB903×343 32.6 KB

3

This is why we need a Home/Reset button to make possible a one-click clearing of all state persistence.

In addition, the 2-min timeout should be user-configurable, and there should be an option to clear all persistence when closing the active browser tab or when switching to a different tab.

3 Likes
4

Ah! that does clarify one thing for me which I didn’t mention in the original post. I have noticed that sometimes the search box is clear and I hadn’t been able to figure out what caused the intermittent behavior
I still prefer the old UI over the persistent UI because for me the overwhelming majority of times that I use the UI I am doing the simple thing of search and launch. Unfortunately it is so common that utilities like bw get features added to improve the experience when the old experience was so good that it didn’t need any improvement.

5

I’d also be happy with the entire search field being “selected”, as if I had typed ctrl-A. If I just start typing, it would then overwrite, but if I hit an arrow key, the cursor moves to the end and I can then append (or prepend) what is already there.

1 Like