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

Anne van Kesteren fora at annevankesteren.nl
Mon Oct 24 01:52:15 PDT 2005

Quoting Ian Hickson <ian at hixie.ch>:
>> # 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 attribute?
>> 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
>> "".
> Your two requests here seem to contradict each other. Could you clarify?

They do? How? You have to add that note because that is what UAs do and after
that you have to change section 2.4 so that the note does not make your
specification contradicting.

>> # 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.
> That XML rule only applies to validating parsers and to parsers exposed to
> internal subsets, IIRC.

Let me quote:

# Before the value of an attribute is passed to the application
# or checked for validity, the XML processor MUST normalize the
# attribute value by applying the algorithm below

(Also, internal subsets are required to be supported by XML parsers.)

Anne van Kesteren

More information about the whatwg mailing list