🚀 Feature: more accurate email validation at sign in and sign up

[donni106]

🔖 Feature description

The sign in and sign up forms validate the email address:

When passing without the ending, i.e. ".com", the validation is missing and the form is sent to the server, which then validates:

The email input could already validate against the full accurate email format.

🎤 Pitch

As the email format will be validates after sending the form anyways and there exists a form input validation in the frontend, it could be extended with the full email format validation including ".com" endings.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[stnguyen90]

@TorstenDittmann, do we want to update the client-side validation for this? According to MDN, something@something is valid:

A single properly-formed email address. This doesn't necessarily mean the email address exists, but it is at least formatted correctly. In simple terms, this means username@domain or [email protected].

[shishir-prasad]

Hi,
I can work on this issue.

[AkashSharma001]

I would like to work on this.
@stnguyen90

[TGlide]

@TorstenDittmann, do we want to update the client-side validation for this? According to MDN, something@something is valid:

A single properly-formed email address. This doesn't necessarily mean the email address exists, but it is at least formatted correctly. In simple terms, this means username@domain or [email protected].

IMO, formatting email client side can lead to errors. There are so many possible ways to write an email, that even this regex doesn't 100% work. There are other issues too.

[donni106]

Anyways I suggest having the same validations in the client and on the server?!

[Nandini99-git]

It looks like you are sign in for the first time. Follow this step

1. click to sign-in now
2. accept the certificate
   and now try to sign up
   I hope this will help.

[TorstenDittmann]

@TorstenDittmann, do we want to update the client-side validation for this? According to MDN, something@something is valid:

A single properly-formed email address. This doesn't necessarily mean the email address exists, but it is at least formatted correctly. In simple terms, this means username@domain or [email protected].

Yeah, let's allow these e-mails. Especially in Windows domain and co its quite common to have these type of e-mails.