Autosave prompt should update email address changes

jcubic · April 17, 2026, 12:47pm

When you change the email/login Bitwarden asks to update the data, but the data is not updated. You need to do this by hand.

I’m not sure if this was something that was working or not. You don’t often change the login. But if you don’t have a feature to update the login, why do you ask to update the data? You give the false impression that you saved something, which is not true.

grb · April 17, 2026, 1:42pm

There is a bug report on Github:

github.com/bitwarden/clients

Unexpected behavior of "Ask to update existing login" when changing username

opened 01:40PM - 17 Apr 26 UTC

bwbug

bug browser

### Steps To Reproduce 1. Enable "Ask to update existing login"; disable "Ask t…o add login". 2. Create at least two login items with different login credentials, but with a common URI `https://fill.dev/form/login-simple`. 3. Navigate the browser to `https://fill.dev/form/login-simple`, and confirm that the login items created in **Step 2** appear as autofill suggestions. 4. Autofill one of the login items. 5. On the web form, manually modify the autofilled _Username_ string, but do not modify the autofilled _Password_ string. 6. Submit the web form. 7. In the Bitwarden "Update existing login" pop-up prompt, click <kbd>Update</kbd>. 8. In the "Login updated" success banner, click **"View"**. 9. In the Bitwarden extension pop-out window, examine the value of the _Username_ field, comparing this to the username value shown in the "Form Submit Results" page on the `fill.dev` site. ### Expected Result One of the following should occur: * There should be no "Update existing login" prompt, because the user may be trying to log in to an account with a different username. * If Bitwarden is able to deduce that the user is intending to modify the username of a specific account (either by seeing an autofill action followed by a form submission with an altered username, with further evidence possibly supplied by identifying the web page as form for changing an account information), then the username in the corresponding vault item should be correctly updated. * If Bitwarden cannot reliably deduce the user's intent, then the prompt should list _all_ matching login items, and give the user an opportunity to select which login item should be updated with the new username. I have no personal preference for which of the above "expected" behaviors should be implemented as a fix, as long as something is done about the _unexpected_ (and faulty) behavior of misleading the user into thinking that the login item username was updated when it in fact was not changed. ### Actual Result The user is shown an "Update existing login" prompt when submitting the form (**Step 6**), followed by a "Login updated" success banner after clicking <kbd>Update</kbd> (**Step 7**). However, examination of the "updated" login item in the vault reveals that the username field was _not_ modified (**Step 9**) ### Screenshots or Videos #### When a new username is submitted, the prompt to update the existing record appears: <img width="999" height="339" alt="Image" src="https://github.com/user-attachments/assets/638625fd-a0b0-4be4-9178-9f63d1a2125e" /> #### When clicking "Update", a success banner appears: <img width="993" height="337" alt="Image" src="https://github.com/user-attachments/assets/fb38017a-4d89-4d98-9ccc-2cc510a1d468" /> #### When clicking "View", the existing vault record shows the original username: <img width="474" height="627" alt="Image" src="https://github.com/user-attachments/assets/48d523b9-0e43-4d0c-a24c-d2c8d8984652" /> ### Additional Context _No response_ ### Operating System Windows ### Operating System Version Windows 11 (24H2) ### Web Browser Chrome ### Browser Version _No response_ ### Environment Versions Version: 2026.3.0; SDK: 'main (7637fdf)'; Server version: 2026.4.0 ### 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.

jcubic · April 17, 2026, 2:48pm

I bet it will be closed soon, the same as my bug report that was reported before.

github.com/bitwarden/clients

Email change is not updated when saving

opened 10:34PM - 16 Apr 26 UTC

closed 04:07AM - 17 Apr 26 UTC

jcubic

bug browser

### Steps To Reproduce 1. Go into the [Manning](https://www.manning.com/) websi…te 2. Log in to your account (you may need to create one) 3. Change email 4. Log out 5. Log in again (use autocomplete) 6. Change email in the form 7. Accept the update of the credentials ### Expected Result I expect the email to be updated ### Actual Result Email is not updated; you need to change it by hand. ### Screenshots or Videos _No response_ ### Additional Context This probably is for every website where you change email, since this is a generic task. And email changes don't happen too often; that's why the bug was not discovered before. ### Operating System Linux ### Operating System Version Fedora ### Web Browser Brave ### Browser Version Brave 1.88.136 (Oficjalna wersja) (64-bitowa) ### Environment Versions Wersja: 2026.3.0 SDK: 'main (7637fdf)' Wersja serwera: 2026.4.0 ### 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.

grb · April 17, 2026, 3:28pm

We’ll see. With the additional detail in the new report, and possible with a different Bitwarden staff member doing the triage, there may be a different outcome.