Issue with Email Sign-Up Due to "+" Character

[ollebergkvist]

We recently received a support ticket from a client who faced difficulties signing up for our app because their email contained a "+". The valibot validation for the email() method prevented the sign-up process.

I'm aware that many email providers do not permit the use of the "+" character. However, I'd like to highlight that reputable providers, such as ProtonMail, now allow its usage in email addresses (https://proton.me/mail).

[ariskemper]

@ollebergkvist could you provide more context, because valibot supports email in format like [email protected] ?

[fabian-hiller]

Thank you for creating this issue. I will take a look at it once we have more details. As a workaround, you can use one of these regex along with our regex validation function:

W3C Working Draft Regex from w3.org:

/^[a-zA-Z0-9.!#$%&’*+/=?^_`{|}~-]+@[a-zA-Z0-9-]+(?:\.[a-zA-Z0-9-]+)*$/

HTML Standard Regex from whatwg.org:

/^[a-zA-Z0-9.!#$%&'*+\/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/

[sqmasep]

@ollebergkvist could you provide more context, because valibot supports email in format like [email protected] ?

It seems that it doesn't work when a + is at the end of the input. If i'm not mistaken, some emails allow this, so that might be the problem

[fabian-hiller]

Thanks for the info. That could be the problem. Let's wait for @ollebergkvist's reply.

[fabian-hiller]

And maybe take a look at issue #204 to understand why email intentionally does not accept every valid email address.

[ariskemper]

@sqmasep @fabian-hiller i added a test here #276 and, it is working for + in the begining and ending of local part. Maybe it is no the issue in '+'character @ollebergkvist? So we would need more context on it.

[ollebergkvist]

Sorry, I've been away for a couple of days.

The email that triggers the error is:
[email protected]

Running:
"valibot": "^0.19.0",

[ollebergkvist]

I invested additional time in debugging the problem. The validation error triggered by valibot for emails with a '+' symbol didn't occur due to the validation process rejecting emails containing '+'. Instead, the issue stemmed from our oversight in encoding/decoding the query parameter passed to valibot. Consequently, valibot misinterpreted the '+' symbol as a space.

Thanks and sorry for the false alarm here!