#13564: Provide class attributes for form fields
-------------------------------+--------------------------------------------
Reporter: h3 | Owner:
Status: new | Milestone: 1.3
Component: Forms | Version: 1.2-beta
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------+--------------------------------------------
Comment (by h3):
> My only concern is the extent to which this masks the bigger issue of
providing an easy way for end-users to customize the exact class names
that are used at time of rendering.
I think this is another issue which is not really an issue. There must be
an easier way to do it, but this is not my point.
If the form fields would be more explicit, for the vast majority of use
cases, this need wouldn't exist altogether. And this step is not that hard
to take, it only
requires to add the field type of the rendered field to its class name.
It's backward compatible, it doesn't brake anything and it solve most
needs for custom class names.
--
Ticket URL: <http://code.djangoproject.com/ticket/13564#comment:3>
Django <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.
