Changes between Initial Version and Version 1 of Ticket #26423, comment 9


Ignore:
Timestamp:
Aug 16, 2016, 12:40:08 AM (8 years ago)
Author:
Jeff Willette

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26423, comment 9

    initial v1  
    22> As discussed on the [https://groups.google.com/d/topic/django-developers/ASBJ0ge2KYo/discussion django-developers mailing list], the regular expressions for validating email addresses are complicated for questionable benefit. We should simplify it to use HTML5 type="email" validation ([http://blog.gerv.net/2011/05/html5_email_address_regexp/ possible candidate]). A deprecation may be needed to give time for projects to add back more complex validation that they might required.
    33
    4 I've found another possible fix here https://html.spec.whatwg.org/multipage/forms.html#valid-e-mail-address, but I have tried this regex and it does not match much out of the ASCII range. What does "HTML5" like browsers match that this regex does not?
     4I've found another possible fix here https://html.spec.whatwg.org/multipage/forms.html#valid-e-mail-address, but I have tried this regex and it does not match much out of the ASCII range. What does "HTML5" like browsers match that this regex does not? if Django wants to accept a large range of unicode characters, why can't it just match the whole unicode range on the local part of the email?
Back to Top