#30776: AuthenticationForm's username field doesn't set maxlength HTML 
attribute.
------------------------------+----------------------------------------
     Reporter:  felixxm       |                    Owner:  Sam Reynolds
         Type:  Bug           |                   Status:  closed
    Component:  contrib.auth  |                  Version:  master
     Severity:  Normal        |               Resolution:  fixed
     Keywords:                |             Triage Stage:  Accepted
    Has patch:  1             |      Needs documentation:  0
  Needs tests:  0             |  Patch needs improvement:  0
Easy pickings:  0             |                    UI/UX:  0
------------------------------+----------------------------------------

Comment (by Sam Reynolds):

 Sorry Carlton. Had I been paying attention to the ticket, I might have
 saved you some pain. I saw the issue with swapping out the field/widget
 when making the change.

 My rationale for sticking with the simpler option was that we can rely on
 the authentication process to ensure the max length of a username. After
 all, if the entered username is longer than the `max_length` of the user
 model, it can't be a validusername!

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30776#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4cf751f14f59cc55f8e59a6fecba55a0%40djangoproject.com.

Reply via email to