#4024: Setting required=True in newforms Fields does not result in an change in
as_p/as_ul/as_table
------------------------------------------------+---------------------------
Reporter: Anders Conbere <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component: django.newforms
Version: SVN | Keywords: html_ouput as_p
as_ul as_table required
Stage: Unreviewed | Has_patch: 1
------------------------------------------------+---------------------------
While it's nice to be able to set "required=True" and have it validate
that properly, there is no hint given to the ui about this. My primary
concern in this case is the generated content from html_output and the
as_* functions. What I propose is a css_classes list in html_output that
can be appended to by other attributes that might be set in the future,
and a classes label for string concatenation added to the normal_row
definitions.
--
Ticket URL: <http://code.djangoproject.com/ticket/4024>
Django Code <http://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 post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
