Autofill usernames more easily

VadeMaecumInfernal · November 14, 2021, 6:01pm

Bitwarden autofill only recognizes password fields on login forms. It doesn’t recognize username fields.

This means that: for 75% of the websites I visit on my phone, Bitwarden will only show the autofill flag when I first tap the password field and then the username field.
Some sites: I tap the password field, then the autofill flag, then select the right login and it fills in both username and password correctly.
Most sites: it only fills in the password field, not the username field and I have to tap on the username field again.

I want: Bitwarden to automatically fill in the username into the username field and then SECONDLY move to the next password field and fill that in.

VadeMaecumInfernal · November 14, 2021, 5:41pm

Bitwarden autofill only recognizes password fields on login forms. It doesn’t recognize username fields.

This means that: for 75% of the websites I visit on my phone, Bitwarden will only show the autofill flag when I first tap the password field and then the username field.
Some sites: I tap the password field, then the autofill flag, then select the right login and it fills in both username and password correctly.
Most sites: it only fills in the password field, not the username field and I have to tap on the username field again.

I want: Bitwarden to automatically fill in the username into the username field and then SECONDLY move to the next password field and fill that in.

How to do:
Bitwarden recognizes every form field on a mobile website as a username field if:
-the text field has the length of only 1 line (like all login forms)
-the text field is placed in the vicinity of a password field, i.e. in front of a password field
-The user has this setting enabled

How to make this SUPER smooth:
-Take the first login that is saved for a website and fill in the username into the username field without even asking. Most of the time people use the same username or email address for every website they visit.

nottabot · November 19, 2021, 3:36pm

This is more of a bug than a feature request. I have the same issue and its quite annoying. I suspect it comes down to how the individual website it coded vs a BitWarden issue.

tgreer · November 19, 2021, 5:34pm

There is actually an open issue on GitHub that covers this and other instances where autofill isn’t behaving as expected.

Please feel free to add information to this issue to help us understand what sites and trends need attention:

github.com/bitwarden/browser

Autofill isn't working for a specific site

opened 09:44PM - 18 Feb 21 UTC

cscharf

enhancement help wanted

## Describe the Bug We are aware of many sites' login forms, payment gateways…, identity forms, etc. where the Bitwarden browser extension either on a single platform/browser or multiple will not autofill information. This is something the Bitwarden team is actively working on but need your help as a community and active Bitwarden users! ## Expected Result When you have autofill configured and get to a page where you have saved credentials within Bitwarden, and your browser extension is unlocked, the credentials should be automatically populated. Otherwise, if you have saved information and use a manual action or command to autofill credentials, identity information, card information, etc.; it should properly populate the form. ## Actual Result This works most of the time, but not always and it can depend on _many, many_ factors. Some sites simply don't work, some don't work consistently and others who knows. This is what we're aiming to fix! ## Call to Action Below is a link to a Google Form that we have created for capturing information that will help us track down all of these pages and forms where Bitwarden has failed to autofill your information. You may submit as many as you like, just please help us help you and the community by providing meaningful information and only those sites/pages where it legitimately doesn't work. [Report autofill failure](https://forms.gle/yYVQkepxxLKZ3kR6A) If you've been sent to this issue because another issue you had open was closed as a duplicate, thank you for taking the time to submit the issue to us, however we truly need to track this under a single item in aggregate fashion so we can manage it holistically and ensure we're taking broad measures that will improve this behavior with the maximum benefit to all. Please consider using the linked form above to submit the prior sites you had reported in the issue closed.

I’ll close this thread as it is indeed an open area of improvement

tgreer · November 19, 2021, 5:34pm