On Friday, April 11, 2014 4:57:33 AM UTC+5:30, Gregor Müllegger wrote: > > I think adding the `required` attribute but ignoring the other possible > html form validations (like `min` and `max` [1] for <input> that are used > by the forms.IntegerField) seems a bit half-hearted. > > My opinion is that having the required attribute is pretty cool, but > should come with all other possible validations baked in then. > django-floppyforms already includes those validations already in the HTML > output of forms and it turns out to be quite useful in many situations. > Even if you turn of the browser validation by adding the novalidate > attribute to the <form> tag, it's good to have this meta data in the HTML > representation, e.g. for styling. > > Gregor >
Thanks Gregor, but I think here we first need to make it clear do we really want it. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/969aae8e-9e07-4e58-96ab-5614436b919e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
