Commit 379bab35 authored by Tim Graham's avatar Tim Graham
Browse files

[1.9.x] Fixed #26265 -- Clarified RadioSelect container's HTML id. 

Backport of 53e8ab58 from master
parent 4e8c2653

docs/ref/forms/api.txt

+5 −0
Original line number Diff line number Diff line
@@ -835,6 +835,11 @@ The field-specific output honors the form object's ``auto_id`` setting:: 
Attributes of ``BoundField``

----------------------------



.. attribute:: BoundField.auto_id



    The HTML ID attribute for this ``BoundField``. Returns an empty string

    if :attr:`Form.auto_id` is ``False``.



.. attribute:: BoundField.data



    This property returns the data for this :class:`~django.forms.BoundField`

docs/ref/forms/widgets.txt

+4 −4
Original line number Diff line number Diff line
@@ -682,8 +682,8 @@ Selector and checkbox widgets 
    simply includes ``{{ myform.beatles }}`` -- they'll be output in a ``<ul>``

    with ``<li>`` tags, as above.



    The outer ``<ul>`` container will receive the ``id`` attribute defined on

    the widget.

    The outer ``<ul>`` container receives the ``id`` attribute of the widget,

    if defined, or :attr:`BoundField.auto_id` otherwise.



    When looping over the radio buttons, the ``label`` and ``input`` tags include

    ``for`` and ``id`` attributes, respectively. Each radio button has an
@@ -704,8 +704,8 @@ Selector and checkbox widgets 
          ...

        </ul>



    The outer ``<ul>`` container will receive the ``id`` attribute defined on

    the widget.

    The outer ``<ul>`` container receives the ``id`` attribute of the widget,

    if defined, or :attr:`BoundField.auto_id` otherwise.



Like :class:`RadioSelect`, you can now loop over the individual checkboxes making

up the lists. See the documentation of :class:`RadioSelect` for more details.