Browser extension doesn't focus on master password input

memeNPC · September 30, 2022, 9:55am

Hey,

I noticed this problem a few days ago and it wasn’t there before.

Before this, here’s what I’d do: I clicked on the Bitwarden icon in Chrome and directly entered my password to unlock the vault (the input was automatically in focus, so I could type inside it without clicking on it or using TAB on my keyboard).

Now, the input doesn’t focus automatically when I open the extension, so I have to manually click on the input or use my keyboard which is really annoying because that’s one more (useless) step to unlock the vault.

Do you know what causes this? I swear this issue wasn’t there a few days ago.

Peter_H · September 30, 2022, 10:18am

It still does focus on the password / PIN field. The thing is it takes a few seconds. Bitwarden is already looking into this. For more details see here:

or here:

github.com/bitwarden/clients

Keyboard Input Lag When Unlocking BW Chrome Extension

opened 07:24PM - 19 Sep 22 UTC

EliasMarine

bug browser

### Steps To Reproduce 1. Go to Chrome/Brave BW extension 2. Click on BW exten…sion to open & unlock with a pin 3. Input unlock pin ### Expected Result The BW extension should accept keyboard input without any lag. ### Actual Result The BW extension has about a ~2-3 second lag before it accepts keyboard input. ### Screenshots or Videos _No response_ ### Additional Context When attempting to unlock the BW chrome extension, there is about a ~3-second lag between when the extension dropdown opens to when it accepts keyboard input. Before the 2022.9 update, I never experienced this lag. In version 2022.8 and older, I would click the extension, and it would start taking input instantly. Looking back at this, this was an unnoticed workflow enhancer, as the vault would unlock pretty quickly. I'm running the BW extension on **Brave Beta Version 1.44.86 Chromium: 105.0.5195.127 (Official Build) beta (arm64)**. This shouldn't matter as I've always run Brave in beta and the BW extension worked flawlessly before 2022.9. & 2022.9.1. I created a new Brave beta profile to test, but still the same thing. I am not using a self-hosted instance. All my browsers are up to date. Once browsers were closed out, there were no lingering processes for Brave or Chrome browsers. I ran the extension on **Chrome Version 105.0.5195.125 (Official Build) (arm64**), and I still get the same input lag issue. I tried on safari, **Version 16.0 (17614.1.25.9.10, 17614)** and input lag is also present there. ### Operating System macOS ### Operating System Version Version 12.6 (21G115) ### Web Browser Brave ### Browser Version Brave Beta Version 1.44.86 Chromium: 105.0.5195.127 (Official Build) beta (arm64 ### Build Version 2022.9.1

P.S.: Changed from Feature Request to Ask the Bitwarden Community.

memeNPC · September 30, 2022, 11:03am

Oh you’re right, it just takes a few seconds to focus which sucks!
Sorry for this useless thread then. It can now be closed

Scott · October 1, 2022, 3:21pm

I came here to report the same issue. It’s really annoying. Thanks for the post.

Technically, the extension’s “title” class object has focus when the extension is first opened, and the cursor is moved after a delay. I’ve found I can either wait a couple seconds for that to happen, hit the Tab key twice, or (of course) click in the PIN text box.

memeNPC · October 1, 2022, 8:47pm

Yeah, I also hit the tab key twice as a workaround for now!
Let’s hope this gets fixed quickly, it shouldn’t be too hard.