benlikescode
commented
1 year ago Thanks for mentioning this, I have updated the email inputs to use type="email" which would address the issue you ran into.
I also updated the autocomplete value for display name which was previously suggesting emails for your username which may be confusing.
Currently, when attempting to log in using a non-email format, the POST login API request is triggered. This could be enhanced by implementing email validation on the login form. This validation would not only prevent the submission of incorrect inputs but also provide a user-friendly warning to users. There may be edge dev cases where you would like to submit non-emails so maybe just a warning could be enough.
it's worth noting that form validations already exists on the change password form by alerting users when their password confirmation doesn't match.
User Experience Improvement: By improving the email validation on the login form, we can address a usability issue that I encountered. During my recent password reset, I ended up resetting my password again, unknowingly, because I missed the requirement for an email input instead of a username.