[x] Keep it as currently implemented EmailAddressValidator is too strict, but at least you can see what it does. The regexp in RfcCompliantEmailAddressValidator is crazy, outdated and probably very inefficient. IMHO, we should mark it as deprecated. The best solution would be to use a parser generator to generate a parser for email addresses.
Best regards, Emond On Friday 20 July 2012 15:25:20 Martin Dilger wrote: > [x] Copy RfcCompliantEmailAddressValidator over EmailAddressValidator, > deprecate RfcCompliantEmailAddressValidator > > > 2012/7/20 Martijn Dashorst <[email protected]> > > > EmailAddressValidator is broken. For example, it doesn't validate > > "Martijn Dashorst <[email protected]>" properly, which is > > standards compliant. Rfc validator does work. The only reason why RFC > > validator was not admitted to core, was its memory consumption due to > > the regular expression. But since RFC is now singleton, I severely > > doubt that is still an issue. > > > > [ ] Copy RfcCompliantEmailAddressValidator over EmailAddressValidator, > > deprecate RfcCompliantEmailAddressValidator > > [ ] Deprecate EmailAddressValidator, move > > RfcCompliantEmailAddressValidator to core, favor RFC in EmailTextField > > [ ] Keep it as currently implemented > > > > Martijn
