@Reporter:
Thanks for filing the issue.

@vasilii:
With reference to Issue: 806530, could you please confirm if the Issue: 811205 is similiar to Issue: 806530

Thanks!

It's indeed similar. The difference is that here the origin is the same. Therefore, there is even stronger signal that both accounts are the same. It's common for the sites to have more than one sign-in form. Thus,  I think that the default behaviour should be as it's today (i.e. update the credential for mywebsite.com). On the other hand, I understand that there are exceptions and we should allow users to handle it in the UI.
We'll brainstorm this problem in the team with UX people.

Thanks to all for recognizing this issue. Yes, domains are the same, but they can be 2 completely different apps altogether (and they actually/usually are). But, Chrome does not understand it and thinks it's the same account with updated password for some reason.

Also, I tried to import my 'Login Data' (passwords) from an older Chrome into the new one (along the journal), but it didn't work, probably because things changed considerably in the meantime. I thought it will let me keep those saved credentials separate if I try it.

Regards

I think import should work. Are you sure you had different URLs in the file?

If you refer to 'Login Data', when I overwrote the files from an old Chrome (v47) into the new Chrome (v63) all saved passwords were lost. URLs are always the same (bookmarks) :)

I meant normal import. You can enable #password-import in chrome://flags/. Then in chrome://settings/passwords you can import the passwords from a text file. For the format you can check the exported file (guarded by #password-export flag).

Thanks, didn't know that. But, we cannot export them this way from an older version/different computer? (I don't wish/like to use cloud). So, what format they should be in txt file?

That feature was in the old versions too (on desktop only). The flag was different though. You can try searching chrome://flags/ for "password". Regarding the format. This is a valid import file

name,url,username,password
some_name_doesnt_matter,https://rsolomakhin.github.io/autofill/,userA,12345
some_name_doesnt_matter,https://rsolomakhin.github.io/autofill/,userB,password123

I just verified that it works.

Thanks, it's good to know :)
Well, I have already manually signed/saved most used ones already, but will do this when I find time later (read: probably never :))

That way you could import two different passwords and check if it works for you temporary.

Thank you, I will definitely try it then!

Just discovered this also affects /localhost/*/, as I have a lot of stuff under different folders, if username collision happens, Chrome will offer update instead. I know it's the same, just thought it was worth mentioning.