Skip to content

fix: #5486 give MultiWidget fields a working label association #5487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mauromsl merged 1 commit into from
Sep 3, 2026
Merged

fix: #5486 give MultiWidget fields a working label association #5487

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/templates/admin/elements/forms/field.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,10 @@
{% get_language_info_list for LANGUAGES as languages %}

<div>
<label for="{{ field.id_for_label }}">
{# A MultiWidget has no single control, so id_for_label is the empty #}
{# string. Fall back to its first subwidget, which Django ids as #}
{# <auto_id>_0, or the label is associated with nothing. See #5486. #}
<label for="{% if field.id_for_label %}{{ field.id_for_label }}{% else %}{{ field.auto_id }}_0{% endif %}">
<strong>
{{ field.label }}
{% if field.field.required %}
Expand Down
Loading