From ff05de760cc4ef4c7f188e163c722ec3bc1f0cbf Mon Sep 17 00:00:00 2001 From: Jon Dufresne Date: Sat, 20 Jan 2018 23:09:10 -0800 Subject: Fixed #29038 -- Removed closing slash from HTML void tags. --- docs/topics/forms/formsets.txt | 66 ++++++++++++++++++++-------------------- docs/topics/forms/index.txt | 10 +++--- docs/topics/forms/media.txt | 32 +++++++++---------- docs/topics/forms/modelforms.txt | 14 ++++----- 4 files changed, 61 insertions(+), 61 deletions(-) (limited to 'docs/topics/forms') diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt index 08c0194e53..cb07e7ad59 100644 --- a/docs/topics/forms/formsets.txt +++ b/docs/topics/forms/formsets.txt @@ -29,8 +29,8 @@ would with a regular form:: >>> formset = ArticleFormSet() >>> for form in formset: ... print(form.as_table()) - - + + As you can see it only displayed one empty form. The number of empty forms that is displayed is controlled by the ``extra`` parameter. By default, @@ -69,12 +69,12 @@ example:: >>> for form in formset: ... print(form.as_table()) - - - - - - + + + + + + There are now a total of three forms showing above. One for the initial data that was passed in and two extra forms. Also note that we are passing in a @@ -103,8 +103,8 @@ gives you the ability to limit the number of forms the formset will display:: >>> formset = ArticleFormSet() >>> for form in formset: ... print(form.as_table()) - - + + If the value of ``max_num`` is greater than the number of existing items in the initial data, up to ``extra`` additional blank forms will be added to the @@ -406,15 +406,15 @@ Lets you create a formset with the ability to order:: ... ]) >>> for form in formset: ... print(form.as_table()) - - - - - - - - - + + + + + + + + + This adds an additional field to each form. This new field is named ``ORDER`` and is an ``forms.IntegerField``. For the forms that came from the initial @@ -466,15 +466,15 @@ Lets you create a formset with the ability to select forms for deletion:: ... ]) >>> for form in formset: ... print(form.as_table()) - - - - - - - - - + + + + + + + + + Similar to ``can_order`` this adds a new field to each form named ``DELETE`` and is a ``forms.BooleanField``. When data comes through marking any of the @@ -540,9 +540,9 @@ default fields/attributes of the order and deletion fields:: >>> formset = ArticleFormSet() >>> for form in formset: ... print(form.as_table()) - - - + + + .. _custom-formset-form-kwargs: @@ -592,14 +592,14 @@ For example, in the default case, you might see: .. code-block:: html - + But with ``ArticleFormset(prefix='article')`` that becomes: .. code-block:: html - + This is useful if you want to :ref:`use more than one formset in a view `. diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt index 86de7d1b06..71d5a37ed9 100644 --- a/docs/topics/forms/index.txt +++ b/docs/topics/forms/index.txt @@ -259,7 +259,7 @@ The whole form, when rendered for the first time, will look like: .. code-block:: html+django - + Note that it **does not** include the ``
`` tags, or a submit button. We'll have to provide those ourselves in the template. @@ -334,7 +334,7 @@ is: {% csrf_token %} {{ form }} - +
All the form's fields and their attributes will be unpacked into HTML markup @@ -512,13 +512,13 @@ Here's the output of ``{{ form.as_p }}`` for our ``ContactForm`` instance: .. code-block:: html+django

-

+

-

+

-

+

Note that each form field has an ID attribute set to ``id_``, which is referenced by the accompanying label tag. This is important in ensuring that diff --git a/docs/topics/forms/media.txt b/docs/topics/forms/media.txt index 28c5054bc3..6b9165339f 100644 --- a/docs/topics/forms/media.txt +++ b/docs/topics/forms/media.txt @@ -71,7 +71,7 @@ can be retrieved through this property:: >>> w = CalendarWidget() >>> print(w.media) - + @@ -114,9 +114,9 @@ requirements:: If this last CSS definition were to be rendered, it would become the following HTML:: - - - + + + ``js`` ------ @@ -145,8 +145,8 @@ example above:: >>> w = FancyCalendarWidget() >>> print(w.media) - - + + @@ -165,7 +165,7 @@ an ``extend=False`` declaration to the ``Media`` declaration:: >>> w = FancyCalendarWidget() >>> print(w.media) - + If you require even more control over inheritance, define your assets using a @@ -228,7 +228,7 @@ was ``None``:: >>> w = CalendarWidget() >>> print(w.media) - + @@ -236,7 +236,7 @@ But if :setting:`STATIC_URL` is ``'http://static.example.com/'``:: >>> w = CalendarWidget() >>> print(w.media) - + @@ -245,7 +245,7 @@ Or if :mod:`~django.contrib.staticfiles` is configured using the >>> w = CalendarWidget() >>> print(w.media) - + @@ -268,12 +268,12 @@ operator to filter out a medium of interest. For example:: >>> w = CalendarWidget() >>> print(w.media) - + >>> print(w.media['css']) - + When you use the subscript operator, the value that is returned is a new ``Media`` object -- but one that only contains the media of interest. @@ -300,7 +300,7 @@ specified by both:: >>> w1 = CalendarWidget() >>> w2 = OtherWidget() >>> print(w1.media + w2.media) - + @@ -362,7 +362,7 @@ are part of the form:: >>> f = ContactForm() >>> f.media - + @@ -382,8 +382,8 @@ form:: >>> f = ContactForm() >>> f.media - - + + diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 3c49e3b8e3..553271e598 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -770,14 +770,14 @@ with the ``Author`` model. It works just like a regular formset:: >>> formset = AuthorFormSet() >>> print(formset) - - + + + .. note:: @@ -959,10 +959,10 @@ so long as the total number of forms does not exceed ``max_num``:: >>> formset = AuthorFormSet(queryset=Author.objects.order_by('name')) >>> for form in formset: ... print(form.as_table()) - - - - + + + + A ``max_num`` value of ``None`` (the default) puts a high limit on the number of forms displayed (1000). In practice this is equivalent to no limit. -- cgit v1.3