#25980: Wrong handling of initial value on disabled ModelMultipleChoiceField
-------------------------------+--------------------------------------
Reporter: karyon | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by karyon):
[https://github.com/django/django/pull/5873 Here] is a PR that adds a test
that verifies that the ModelMultipleChoiceField can handle querysets when
cleaning, because this is what happens when the field is disabled and has
a queryset as initial value, see
[https://github.com/django/django/blob/d91cc25a2a43cb2526943dc2285ffe59e38fabfd/django/forms/forms.py#L372
code]. I still don't know whether this properly reflects the intended
behaviour.
The test might be "too small" to properly explain my problem, as it tests
only the field, not the form... let me know if i should add another test.
--
Ticket URL: <https://code.djangoproject.com/ticket/25980#comment:7>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c46ccdb88d75031d82fe9c8e847a6e8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
