After installing the beta extension I was unable to login to my vault anymore. 
Did I install a malicious app? No, I checked the Chrome store for the “trusted” icon.
So what happened? Apparently the beta extension fills in my e-mail for the “master password” input field. 
Did you select EU or COM, as appropriate?
Are you hosting in the cloud or self-hosting?
Is capslock set?
Are you using an iPhone and have punctuation characters in your password?
Try logging into the webvault using a password that you type into notepad (so you can verify it is OK) and then paste into the webvault’s login. This will ensure you know your password and that the “server side” is OK.
Sorry, my message may not have been as clear as I thought. The login to my vault with the correct master password still works.
However, when I try to use the beta extension to fill-out the master password, it only offers the e-mail address. Since I did not look close enough on the first try, the login fails because my e-mail address is of course not the correct password.
My question is: Why is the beta extension using my e-mail address for the same web page when the original extension would use the master password for the form field?
@marlin I moved your comments into a new topic, because I’m trying to keep the beta feedback thread focused on specific feedback about the UI design of the new browser extension.
Can you please confirm the following?
You are not self-hosted.
You are/were having trouble autofilling the password input field on the Web Vault login form, when using the beta version of the Bitwarden extension.
You are autofilling using the inline autofill menu, and you have enabled “Show autofill suggestions on form fileds” under Settings > Autofill.
I have tried to reproduce your observation, and have been unable to do so.
Are you sure that it is Bitwarden that is inserting your email address into the password field? Do you have any other password managers installed, or are any of your browser’s native autofilling functions still enabled?
Yes to all three items. I am using bitwarden.eu, I had trouble with autofill and the setting was enabled as described.
After restarting my computer this morning, the issue is gone and I cannot reproduce it anymore. Perhaps this was a one-time glitch produced by the new installation and disabling the old extension?
Yes, I am sure, because I clicked on the autofill popup which has been rendered by the extension. I also used the autofill button in den extension itself, that inserted the password correctly. The only thing that did not work was the autofill popup at the form field.
There are no other password managers installed and the password feature of my browser is disabled. I am using Brave by the way.
Good to hear that the issue disappeared.
Well, I was just able to reproduce the issue. The extension does not have to be reinstalled to trigger it.
Steps to reproduce:
Environment: Brave 1.71.114 on Arch Linux
I’ve tried the above, but it autofills the password for me.
Perhaps some subtle differences between Brave and Chrome?
Have you confirmed that this issue does not occur using the regular, non-beta version of the browser extension?
Good thinking, just tested it by disabling the beta extension and re-enabling the stable one. The issue is not present with the stable extension after logout and login, the password is autofilled.
Switched back to the beta extension, same behavior as before, the e-mail is autofilled instead.
I would suggest testing the beta version in a Chrome browser, if you have one available.
I just tested it with a fresh profile in Chromium, the open source base for Chrome. The issue exists there too, so this is not just limited to Brave.
Limiting the tests to Chrome would mean that issues found with other browsers are likely to persist until a stable version is released, impacting a much larger userbase.
I wasn’t suggesting that you limit your tests, but rather expanding your test from Brave (or similar Chromium-based browsers) to also include Chrome proper. This would tell you/us unequivocally whether the issue is caused by a broad-based browser incompatibility or some idiosyncrasy in your setup.
Sorry for the misunderstanding.
I just installed Chrome v130.0.6723.58 and I can confirm that it is affected, too. So I think we can rule out the browser.
Sounds good. Next test I would suggest is to (temporarily) disable the inline suggestions, and instead autofill using Ctrl+Shift+L, or using the right-click menu, or using Autofill on Page Load, or using some of the other autofilling methods. Does the issue occur only when using the inline menus, or also when using other autofilling techniques?
I think I found a way that you can reproduce this on your system, too. It seems that the extension gets confused when the e-mail address is entered manually.
Please try this:
Another observation: There seems to be a difference if I confirm the e-mail with “Enter” (wrong behavior) or by clicking “Continue” (correct behavior).
Shortest way for a reproduction with “Remember email” turned on:
This is my test entry:
Entering the email address manually, and clicking Continue:
Clicking on the suggested account in the inline menu:
Result of autofill:
What happens if you do not press Continue but Enter instead?
OK, yes, this is what makes the difference. I was able to reproduce it on Chrome now.
It seems to be an “edge case”, which requires the username to be submitted using Enter and the inline autofill menu is set to be shown when the input filed is in focus.
If you enable “Display suggestions when icon is selected”, or if you autofill using any other technique, then the behavior is not triggered. And, as you pointed out, if you autofill the username, or if you enter it manually but click Continue instead of hitting the Enter, then then behavior is also not triggered.
It may be worthwhile submitting a bug report on Github, even though this is a beta version.
