Beta Extension: Autofill uses username instead of password

[windmueller]

Steps To Reproduce

1. Store the Bitwarden credentials in your vault
2. Go to 'https://vault.bitwarden.eu/' (or .com)
3. If your e-mail address is remembered, click into the form field. Otherwise, type your e-mail address manually.
4. Do not click on "Continue" but press "Enter"
5. Try to use autofill on the next page

Expected Result

Autofill inserts the password.

Actual Result

Autofill inserts the login e-mail address.

Screenshots or Videos

No response

Additional Context

I was able to reproduce this issue in Brave, Chromium and Chrome. Please see the discussion in the community portal for details.

Operating System

Linux

Operating System Version

No response

Web Browser

Brave

Browser Version

Version 1.71.114

Build Version

2024.10.999

Issue Tracking Info

• [X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system. ID: PM-13863

[bwbug]

As noted in the related discussion in the Community Forum, reproducing this bug also requires the Autofill settings to be configured such that "Show autofill suggestions on form fields" is enabled, but “Display suggestions when icon is selected” is disabled; the autofill action (Step 5 in the "Steps to Reproduce") must be done by clicking the suggested credential in the inline autofill menu in the master password input field.

I can reproduce this behavior in Chrome on Windows 11.

[Krychaz]

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

[bwbug]

@Krychaz How come some bug reports for the beta extension are welcomed and acted upon here (like this one), while others are immediately closed as "not planned" just because it is not an issue in the production version of the extension?