Current bug: Browser extensions no longer focus on search field

I could have swore that about a week of two ago - when I clicked on the Bitwarden “shield” in my Edge toolbar and the extension folds down - my cursor used to automatically be placed in the Search box and I could simply start typing for a password/site.

Now - I need to place it manually each time - which felt a little odd when I realized I had to do ths every time.

Or am I seeing things?

S

3 Likes

It works properly for me, but not the first time immediately after logging in.

Extension 2025.3.1
Edge 135.0.3179.54
Window 11 24h2

Standard troubleshooting steps:

  1. Lock and unlock
  2. Logout and log back in
  3. Uninstall and Reinstall
  4. Uninstall, remove local storage and reinstall.

Feel free to skip steps 1-3 if you are OK with resetting your defaults.

@Sonicmojo @DenBesten Just a thought: I guess, the Edge extension is already on 2025.3.2 and this could be a new behaviour…

Uninstalled 2025.3.1 and installed 2025.3.2. The cursor is no longer in the search field for me either. Instead, I need to either press tab 4 times or click in the field.

Just created a bug report. Feel free to pile onto it. Edge no longer focuses on Search field · Issue #14147 · bitwarden/clients · GitHub

1 Like

… we’ll see in the next days, if it’s just Edge…

2025.3.2 is there for the Chrome Store… seeing the same thing now in other browsers… (later, I might add it on GitHub)

Thanks guys! Appreciate your efforts.

S

when pressing [⌘⇧Y] to enable the browser extension on bitwarden (on Chrome), why isn’t it automatically in the search field like it was before, is this removed??? Why, I don’t want to waste time, I want to search automatically.

There is a bug report about that:

1 Like

IIRC this was default behavior before the new UI overhaul, but when clicking the browser extension button (Chrome) typing does nothing. I now have to either use the mouse to move and click in, or type “Tab” 4 times to reach the “Search” field.

It would be snappy and quick to (once again?) be able to click the extension, move my hands to keyboard, and start typing the Search query I’m looking for.

Thanks!

@honmashinsei Welcome to the forum!

I moved your post into this existing thread to the same topic.

PS: See the bug report for this in this post by @DenBesten.

Note: I changed the title of this topic now, to reflect the actual issue - and to improve “findability”. (before, it was: “Has something changed recently in the Edge Web Extension?”)

thank you! i searched but couldn’t find any similar posts.

i’d like to add that i think the following is new behavior as well:
when typing something into the search field, exiting the extension popup, then reopening the extension popup keeps the previous search term in the search field instead of clearing it (even when switching between tabs!) > pretty useless behavior imo and adds unnecessary keystrokes or clicks to empty it out.

That is a different thing - and probably get’s cleared up with this bug report (also see the comments below there): Vault search field and results do not clear when re-opening the plugin · Issue #14247 · bitwarden/clients · GitHub

I was just coming to report this issue. I’m glad to see it’s already here (and it’s not just me).

In case it helps, I’m seeing this in Bitwarden using Firefox, Vivaldi, and Brave browsers, all on Linux Mint OS.

Bitwarden info:
Version: 2025.3.2
SDK: ‘main (50f5a17)’
Server version: 2025.3.3

When clicking the browser extension button (Chrome) typing does nothing. I now have to either use the mouse to move and click in to enter the search field

It would be quicker (less work) be able to click the extension, move my hands to keyboard, and start typing the Search query I’m looking for.

@carlvanwormer Welcome to the forum!

@artush @carlvanwormer I moved your posts into this existing topic to this current bug… Here is the corresponding bug report on GitHub:

That is the reason for this thread. Hopefully a fix is coming soon. This is maddening - considering it was just fine about 6 weeks ago.

S

This bug started with extension version 2025.3.2, which was released on Apr 3 – so it was fine 2 weeks ago

Or actually anytime before April 3 - is what I meant generally…

S