#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 Claude Paroz):
I'm not yet sure about the implementation (didn't find time until now),
but basically, we should be able to handle the following use cases:
- attrs for parent widget, not on subwidgets (already OK with
`option_inherits_attrs` set to `False`)
- same attrs for parent widget AND subwidgets (already OK with
`option_inherits_attrs` set to `True`)
- attrs for subwidgets but NOT for parent widget (<-- TODO)
Ideally I would like to be able to do that without subclassing, e.g. by
`Widget(attrs={...}, option_attrs={...})`. I guess experiments will tell
if it's doable wrt option attrs inheritance.
--
Ticket URL: <https://code.djangoproject.com/ticket/34034#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018384241b7e-5e3664fc-af22-4187-95e4-39b8c46c6745-000000%40eu-central-1.amazonses.com.
