mirror of https://github.com/django/django.git
[1.5.x] Fixed #19812 - Removed a duplicate phrase in the widget docs.
Thanks diegueus9 for the report and itsallvoodoo for the draft patch.
Backport of 7a80904b00
from master
This commit is contained in:
parent
5c3c8bf09a
commit
ad2b091c1f
|
@ -279,15 +279,10 @@ foundation for custom widgets.
|
||||||
* A single value (e.g., a string) that is the "compressed" representation
|
* A single value (e.g., a string) that is the "compressed" representation
|
||||||
of a ``list`` of values.
|
of a ``list`` of values.
|
||||||
|
|
||||||
If `value` is a list, output of :meth:`~MultiWidget.render` will be a
|
If ``value`` is a list, the output of :meth:`~MultiWidget.render` will
|
||||||
concatenation of rendered child widgets. If `value` is not a list, it
|
be a concatenation of rendered child widgets. If ``value`` is not a
|
||||||
will be first processed by the method :meth:`~MultiWidget.decompress()`
|
list, it will first be processed by the method
|
||||||
to create the list and then processed as above.
|
:meth:`~MultiWidget.decompress()` to create the list and then rendered.
|
||||||
|
|
||||||
In the second case -- i.e., if the value is *not* a list --
|
|
||||||
``render()`` will first decompress the value into a ``list`` before
|
|
||||||
rendering it. It does so by calling the ``decompress()`` method, which
|
|
||||||
:class:`MultiWidget`'s subclasses must implement (see above).
|
|
||||||
|
|
||||||
When ``render()`` executes its HTML rendering, each value in the list
|
When ``render()`` executes its HTML rendering, each value in the list
|
||||||
is rendered with the corresponding widget -- the first value is
|
is rendered with the corresponding widget -- the first value is
|
||||||
|
|
Loading…
Reference in New Issue