[whatwg] [wf2] 2.3. Changes to existing controls

Anne van Kesteren fora at annevankesteren.nl
Sun Oct 23 03:55:15 PDT 2005

# Form controls by default associate with their nearest form
# ancestor.

Could this sentence be made more normative? That it actually is a requirement
unless the control has a 'form' attribute specified. That in that case the
rules for that apply.

# The label element's exact default presentation and behaviour
# should match the platform's label behaviour. For example, on
# platforms where clicking a checkbox label checks the
# checkbox, clicking a label element must cause a click event
# to be synthesised and fired at the checkbox.

First 'should', later 'must'. Please change either one of them.

# No click event is fired in this case.

"must be fired"?

# so that if the value content attribute is not specified then
# the value DOM attribute (and the value used for submission
# when the controls are checked) is "on".

Could you perhaps add that setting the value content attribute to the empty
string must not be considered differently from setting the value content

Note that in order to do that you would also have to change section 2.4 which
states that setting value to the empty string means "no value selected". That
would result in the value used for submission being "on" which is not what user
agents currently do, or are supposed to do. value="" should not result in the
value DOM attribute being "on", but "".

# Whitespace must also not be trimmed from any other attributes
# (e.g. the value attribute).

Could you add a note that there is some form of normalization applied to these
attributes in XML documents as described here:
<http://www.w3.org/TR/REC-xml/#AVNormalize>. This could be helpful and would
prevent confusion.



Anne van Kesteren

More information about the whatwg mailing list