Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#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)

comment:1 by Luke Plant, 14 years ago

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.

in reply to:  1 comment:2 by Skylar Saveland, 14 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.

in reply to:  1 ; comment:3 by Karen Tracey, 14 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.

in reply to:  3 comment:4 by Luke Plant, 14 years ago

Owner: changed from nobody to Luke Plant
Status: newassigned

Replying to kmtracey:

It's doctype-dependent:

http://www.w3.org/TR/xhtml1/#h-4.2

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:5 by Luke Plant, 14 years ago

Fixed in [12086]. (Typo in that commit message closed the wrong bug)

comment:6 by Luke Plant, 14 years ago

Resolution: fixed
Status: assignedclosed

(In [12087]) [1.1.X] Fixed #12503 - form examples don't validate according to w3c

Thanks to skyl for the report.

Backport of r12086 from trunk

comment:7 by Karen Tracey, 14 years ago

Replying to lukeplant:

Replying to kmtracey:

It's doctype-dependent:

http://www.w3.org/TR/xhtml1/#h-4.2

That's about attribute names, not values.

Hmm, so it is. And in a brief scan I can't find where it says anything similar for values. Validator a bit over-zealous maybe?

Note: See TracTickets for help on using tickets.
Back to Top