News for hackers. Stuff that matters.

A comment on The “Chad” bug. Parent comment

Re:The “Chad” bug by zurn on Thursday December 31, 2015 @12:56AM (#10816421)
The email input regexp is only about matching the atext@domain subpart of the syntax. The full email address parsers are about parsing the full allowed syntax you can put in an email to: field that includes address lists and display names.

Also W3C produced HTML specs are hardly gospel about email-related things (but I don't know whether there's anything wrong in this case).

[ Parent | on HN ]
Re:The “Chad” bug by zurn on Thursday December 31, 2015 @07:43AM (#10817374)
Replying to myself (can't edit anymore), looks like the W3C spec bungled it in your [1] by referencing "atext" from the RFC. For example, as specified it disallows addresses with periods in them. In the RFC, "atext" is just a building block in the syntax of the local-part before @ sign.
[ Parent | on HN ]
Re:The “Chad” bug by kccqzy on Thursday December 31, 2015 @06:33AM (#10817206)
But the question is, if a signup form is asking for your email address, will you type in your name, a pair of angle brackets, and then your email address in between? That's simply not what the web developer wants here.
[ Parent | on HN ]
Re:The “Chad” bug by lmm on Thursday December 31, 2015 @12:01PM (#10818431)
Will I type that in? No. Will I copy-paste my email from my address book program? Quite possibly.
[ Parent | on HN ]