Author: lukeplant
Date: 2010-01-04 16:22:16 -0600 (Mon, 04 Jan 2010)
New Revision: 12087
Modified:
django/branches/releases/1.1.X/
django/branches/releases/1.1.X/django/contrib/comments/templatetags/comments.py
django/branches/releases/1.1.X/django/contrib/csrf/tests.py
django/branches/releases/1.1.X/docs/ref/contrib/comments/index.txt
django/branches/releases/1.1.X/docs/topics/forms/formsets.txt
django/branches/releases/1.1.X/docs/topics/forms/index.txt
django/branches/releases/1.1.X/docs/topics/forms/modelforms.txt
Log:
[1.1.X] Fixed #12503 - form examples don't validate according to w3c
Thanks to skyl for the report.
Backport of r12086 from trunk
Property changes on: django/branches/releases/1.1.X
___________________________________________________________________
Name: svnmerge-integrated
-
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11961,12011
+
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11961,12011,12086
Modified:
django/branches/releases/1.1.X/django/contrib/comments/templatetags/comments.py
===================================================================
---
django/branches/releases/1.1.X/django/contrib/comments/templatetags/comments.py
2010-01-04 21:55:52 UTC (rev 12086)
+++
django/branches/releases/1.1.X/django/contrib/comments/templatetags/comments.py
2010-01-04 22:22:16 UTC (rev 12087)
@@ -248,7 +248,7 @@
Example::
- <form action="{% comment_form_target %}" method="POST">
+ <form action="{% comment_form_target %}" method="post">
"""
return comments.get_form_target()
Modified: django/branches/releases/1.1.X/django/contrib/csrf/tests.py
===================================================================
--- django/branches/releases/1.1.X/django/contrib/csrf/tests.py 2010-01-04
21:55:52 UTC (rev 12086)
+++ django/branches/releases/1.1.X/django/contrib/csrf/tests.py 2010-01-04
22:22:16 UTC (rev 12087)
@@ -9,7 +9,7 @@
def post_form_response():
resp = HttpResponse(content="""
-<html><body><form method="POST"><input type="text" /></form></body></html>
+<html><body><form method="post"><input type="text" /></form></body></html>
""", mimetype="text/html")
return resp
Modified: django/branches/releases/1.1.X/docs/ref/contrib/comments/index.txt
===================================================================
--- django/branches/releases/1.1.X/docs/ref/contrib/comments/index.txt
2010-01-04 21:55:52 UTC (rev 12086)
+++ django/branches/releases/1.1.X/docs/ref/contrib/comments/index.txt
2010-01-04 22:22:16 UTC (rev 12087)
@@ -157,7 +157,7 @@
A complete form might look like::
{% get_comment_form for event as form %}
- <form action="{% comment_form_target %}" method="POST">
+ <form action="{% comment_form_target %}" method="post">
{{ form }}
<tr>
<td></td>
@@ -178,7 +178,7 @@
form. This will always return the correct URL that comments should be posted
to;
you'll always want to use it like above::
- <form action="{% comment_form_target %}" method="POST">
+ <form action="{% comment_form_target %}" method="post">
Redirecting after the comment post
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Modified: django/branches/releases/1.1.X/docs/topics/forms/formsets.txt
===================================================================
--- django/branches/releases/1.1.X/docs/topics/forms/formsets.txt
2010-01-04 21:55:52 UTC (rev 12086)
+++ django/branches/releases/1.1.X/docs/topics/forms/formsets.txt
2010-01-04 22:22:16 UTC (rev 12087)
@@ -355,7 +355,7 @@
.. code-block:: html+django
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset.management_form }}
<table>
{% for form in formset.forms %}
@@ -369,7 +369,7 @@
.. code-block:: html+django
- <form method="POST" action="">
+ <form method="post" action="">
<table>
{{ formset }}
</table>
Modified: django/branches/releases/1.1.X/docs/topics/forms/index.txt
===================================================================
--- django/branches/releases/1.1.X/docs/topics/forms/index.txt 2010-01-04
21:55:52 UTC (rev 12086)
+++ django/branches/releases/1.1.X/docs/topics/forms/index.txt 2010-01-04
22:22:16 UTC (rev 12087)
@@ -172,7 +172,7 @@
example, we passed our ``ContactForm`` instance to the template using the
context variable ``form``. Here's a simple example template::
- <form action="/contact/" method="POST">
+ <form action="/contact/" method="post">
{{ form.as_p }}
<input type="submit" value="Submit" />
</form>
@@ -183,7 +183,7 @@
``form.as_p`` will output the form with each form field and accompanying label
wrapped in a paragraph. Here's the output for our example template::
- <form action="/contact/" method="POST">
+ <form action="/contact/" method="post">
<p><label for="id_subject">Subject:</label>
<input id="id_subject" type="text" name="subject" maxlength="100" /></p>
<p><label for="id_message">Message:</label>
@@ -211,7 +211,7 @@
the way a form is presented using the Django template language. Extending the
above example::
- <form action="/contact/" method="POST">
+ <form action="/contact/" method="post">
<div class="fieldWrapper">
{{ form.subject.errors }}
<label for="id_subject">E-mail subject:</label>
@@ -263,7 +263,7 @@
duplicate code by looping through each field in turn using a ``{% for %}``
loop::
- <form action="/contact/" method="POST">
+ <form action="/contact/" method="post">
{% for field in form %}
<div class="fieldWrapper">
{{ field.errors }}
@@ -322,7 +322,7 @@
``visible_fields()``. Here's a modification of an earlier example that uses
these two methods::
- <form action="/contact/" method="POST">
+ <form action="/contact/" method="post">
{% for field in form.visible_fields %}
<div class="fieldWrapper">
@@ -356,7 +356,7 @@
can reduce duplication by saving the form's loop in a standalone template and
using the :ttag:`include` tag to reuse it in other templates::
- <form action="/contact/" method="POST">
+ <form action="/contact/" method="post">
{% include "form_snippet.html" %}
<p><input type="submit" value="Send message" /></p>
</form>
@@ -373,7 +373,7 @@
If the form object passed to a template has a different name within the
context, you can alias it using the :ttag:`with` tag::
- <form action="/comments/add/" method="POST">
+ <form action="/comments/add/" method="post">
{% with comment_form as form %}
{% include "form_snippet.html" %}
{% endwith %}
Modified: django/branches/releases/1.1.X/docs/topics/forms/modelforms.txt
===================================================================
--- django/branches/releases/1.1.X/docs/topics/forms/modelforms.txt
2010-01-04 21:55:52 UTC (rev 12086)
+++ django/branches/releases/1.1.X/docs/topics/forms/modelforms.txt
2010-01-04 22:22:16 UTC (rev 12087)
@@ -697,14 +697,14 @@
First, you can let the formset do most of the work::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset }}
</form>
Second, you can manually render the formset, but let the form deal with
itself::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{{ form }}
@@ -717,7 +717,7 @@
Third, you can manually render each field::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{% for field in form %}
@@ -730,7 +730,7 @@
a ``{% for %}`` loop, you'll need to render the primary key field. For example,
if you were rendering the ``name`` and ``age`` fields of a model::
- <form method="POST" action="">
+ <form method="post" action="">
{{ formset.management_form }}
{% for form in formset.forms %}
{{ form.id }}
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
