#10928: BooleanField: different behaviour when default=callable
-------------------------------------+--------------------------------------
Reporter: a...@gc-web.de | Owner: nobody
Status: new | Milestone:
Component: Uncategorized | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by a...@gc-web.de):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Oh, hit submit too fast. Basically, the callable-form emits, when used in
a ModelForm (for example the admin), the following hidden initial-field:
{{{
<input type="hidden" name="initial-child1_set-0-foo" value="False"
id="id_child1_set-0-foo" />
}}}
This has the effect that {{{form.has_changed()}}} is always True, so that
extra forms of formsets are always considered for validation.
--
Ticket URL: <http://code.djangoproject.com/ticket/10928#comment:1>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
