#35870: Allow customization of the blank option in select dropdowns
-------------------------------------+-------------------------------------
Reporter: Marijke Luttekes | Owner: Marijke
| Luttekes
Type: Bug | Status: assigned
Component: Forms | Version: 5.0
Severity: Normal | Resolution:
Keywords: accessibility | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marijke Luttekes):
Update: I created [[https://github.com/django/django/pull/18924|PR
#18924]] with a fix, assisted by Carlton.
We initially wanted to use a form renderer to set the value, but we had to
resort to a setting.
The PR has details, but the short version is that not every implementation
of a blank choice has access to the form renderer.
We concluded that this change is so impactful and close to the 5.2 feature
freeze that we must postpone it until the 6.0 release.
I checked if we could make a separate change for 5.2 that would allow
users to monkey-patch the label; sadly, this isn't an option.
Blank choice values get defined in multiple locations, including once in a
place that makes it hard to import into several form-related modules
(hence the multiple existing declarations).
So for now, we will have to put this issue on hold.
--
Ticket URL: <https://code.djangoproject.com/ticket/35870#comment:17>
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 visit
https://groups.google.com/d/msgid/django-updates/01070193eb2978ad-a8164879-b090-418b-8371-d77208aa4b10-000000%40eu-central-1.amazonses.com.
