#12503 closed (fixed)
Form examples don't use w3c validating markup
Reported by: | Skylar Saveland | Owned by: | Luke Plant |
---|---|---|---|
Component: | Uncategorized | Version: | 1.1 |
Severity: | Keywords: | docs w3c | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Examples in the docs like:
http://docs.djangoproject.com/en/dev/topics/forms/#displaying-a-form-using-a-template
use method="POST"
whereas w3c specifies
method="post"
.
Change History (7)
follow-ups: 2 3 comment:1 by , 15 years ago
comment:2 by , 15 years ago
Replying to lukeplant:
Hmm, w3c docs says it is case insensitive: http://www.w3.org/TR/html4/interact/forms.html#adef-method
But the w3c validator does indeed complain at upper case.
My mistake if this is not legitimate. I suppose it is a bug in the validator rather than the django docs.
follow-up: 4 comment:3 by , 15 years ago
Replying to lukeplant:
Hmm, w3c docs says it is case insensitive: http://www.w3.org/TR/html4/interact/forms.html#adef-method
But the w3c validator does indeed complain at upper case.
It's doctype-dependent:
http://www.w3.org/TR/xhtml1/#h-4.2
Lower case is more broadly acceptable so should probably be used in the docs.
comment:4 by , 15 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Replying to kmtracey:
It's doctype-dependent:
That's about attribute names, not values. But:
Lower case is more broadly acceptable so should probably be used in the docs.
Agreed, I'll fix it.
comment:6 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Hmm, w3c docs says it is case insensitive: http://www.w3.org/TR/html4/interact/forms.html#adef-method
But the w3c validator does indeed complain at upper case.