Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 584bd14dcfdee9585fec7794d53ce120ea73d0bc
https://github.com/django/django/commit/584bd14dcfdee9585fec7794d53ce120ea73d0bc
Author: Gabe Jackson <[email protected]>
Date: 2013-06-10 (Mon, 10 Jun 2013)
Changed paths:
M django/forms/forms.py
M docs/ref/forms/api.txt
M docs/releases/1.6.txt
M docs/topics/forms/index.txt
M docs/topics/forms/modelforms.txt
M tests/admin_util/tests.py
M tests/forms_tests/tests/test_forms.py
M tests/forms_tests/tests/test_regressions.py
Log Message:
-----------
Fixed #18134 -- BoundField.label_tag now includes the form's label_suffix
There was an inconsistency between how the label_tag for forms were
generated depending on which method was used: as_p, as_ul and as_table
contained code to append the label_suffix where as label_tag called on a
form field directly did NOT append the label_suffix. The code for
appending the label_suffix has been moved in to the label_tag code of
the field and the HTML generation code for as_p, as_ul and as_table now
calls this code as well.
This is a backwards incompatible change because users who have added the
label_suffix manually in their templates may now get double label_suffix
characters in their forms.
--
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/51b6199edc512_37961311dd8129551%40hookshot-fe4-pe1-prd.aws.github.net.mail?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
