Prompted to save autofilled credentials when there are multiple entries at the same URL
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 397
Description
### Steps To Reproduce
1. Create two entries for the same URL that points to a login form, but with different credentials
2. Go to the saved URL
3. Fill in one of the entries
4. Log in
### Expected Result
No extra prompts
### Actual Result
There's a prompt to save an "updated password". When clicking Edit on the prompt, it shows that it's the other entry - not the one that was used to fill in the credentials.
### Screenshots or Videos
_No response_
### Additional Context
A similar old issue that doesn't have a lot of details: #461 (linking so it's easier to find this one).
It's hard to say which factors are important, so I'll list everything I know:
- The URL in question is my router's, `192.168.1.1`. Just like that, with no protocol
- The entry that I use all the time has only a password saved - there's no login
- The old entry that I don't use and that receives the update prompt has both a login and a password
- The login in the old entry is the same as the one presented by default by the router's login page, `root`
### Operating System
Linux
### Operating System Version
_No response_
### Web Browser
Chrome
### Browser Version
_No response_
### Build Version
2024.12.4
### 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.
Contributor guide
Research direction
Reproduce this in the Chrome extension on Linux with two Bitwarden entries for the same URL and different credentials, using the router scenario described. Trace the autofill flow and the subsequent updated-password prompt to determine why the other entry is selected; done means logging in after autofill produces no extra prompt and does not modify the unused entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100