The user already entered her email address, she doesn't want to remember a username which doesn't mean anything to her.
Let's log in with an email address and avoid having to remember something else. This leads to confusing.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Quick question though: is there anything preventing a user to adopt an email as a login? I'm thinking about the very unlikely event where user A with email a@a.tld adopts b@b.tld as a login whereas there is an actual user B with email b@b.tld in the userbase. Does someone knows how to handle that?
By Christophe Henry on 2019-10-23T08:33:25 (imported from GitLab project)
I looked into it yesterday afternoon. Solution is not right. Nothing prevents user A to set b@b.tld as a username and then user B to register with b@b.tld as an email. Solution 1 seems to be the way to go.
By Christophe Henry on 2019-10-24T08:06:03 (imported from GitLab project)
Fyi, there is already an implementation of that in Django. I'm not sure how they dealt with this issue, but it might be worth looking into it. It doesn't seem major to me at this time though.