#28480: Nonstandard "minlength" property to <input/>
-------------------------------------+-------------------------------------
     Reporter:  Tomáš Pecina         |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Forms                |                  Version:  1.11
     Severity:  Normal               |               Resolution:  invalid
     Keywords:  minlength input      |             Triage Stage:
  form field                         |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tomáš Pecina):

 That's a good point, Claude. HOWEVER, we should realize that minlength is
 not the same thing as maxlength, conceptually, and browser developers are
 right in not implementing the former very eagerly. With maxlength, there
 is a clear and evident visual and possibly acoustic feedback: when the
 limit is reached, the user's keypresses are not displayed, and perhaps, a
 warning beep is produced. On the other hand, there is no such aid with
 minlength. Therefore, it might be wiser to let the Django validator do the
 job, and inform the user by a message such as "Currency code must consist
 of exactly three characters." By hardcoding the minlength property (which
 is not that easy to remove), we may be doing a disservice to the
 application developer. Please, give the issue a second thought.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28480#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f7e10746af9853b2b15b111bb3440359%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to