3 ms·
Also relevant was, "If you have a well laid-out form with a label that says “email”, and the user enters an ‘@’ symbol somewhere, then it’s safe to say they und
by tempestn 10y ago
Also relevant was, "If you have a well laid-out form with a label that says “email”, and the user enters an ‘@’ symbol somewhere, then it’s safe to say they understood that they were supposed to be entering an email address."
In other words, it does make sense to check that they entered an '@' symbol somewhere, since it shows that they understood it was an email field. Any 'validation' beyond that is useless.
- danso 10y agoHow about more than one @ sign? Does the email address spec exclude the possibility of more than one @ symbols?
- kej 10y agoNope, that's valid if one of them is quoted: "very.unusual.@.unusual.com"@example.com
- deleted 10y ago[deleted]
- tempestn 10y agoIt doesn't matter. If they have typed an @, they probably understand that it's an email field. Trying to validate to the spec beyond that is pointless, for reasons thoroughly covered in the article.
- zeveb 10y agoThe local-part may contain a quoted @: "@"@example.invalid is a valid email address. @ signs are also permitted in comments: (ted@home)ted@example.invalid is also a valid email address.
- ediblenergy 10y agoIt actually used to (maybe still does) signal routing information[1]. An example from the RFC is "@ONE,@TWO:JOE@THREE" [1]: https://tools.ietf.org/html/rfc821 https://tools.ietf.org/html/rfc821