#34034: Adding a class on ChoiceWidget subwidgets is excessively difficult
------------------------------+------------------------------------
Reporter: Claude Paroz | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by David Smith):
Seems a reasonable suggestion to me.
One other thought I had was about using templates. A custom template could
be provided to `option_template_name` or
`"django/forms/widgets/select_option.html"` could be overridden. This may
help to avoid `Widget(attrs={...}, option_attrs={...})` each time this
type of widget is used in a project?
--
Ticket URL: <https://code.djangoproject.com/ticket/34034#comment:5>
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/010701841034fec5-b12bb7b7-e439-4fb6-9dce-98fa954117d8-000000%40eu-central-1.amazonses.com.
