- From: Simon Pieters <simonp@opera.com>
- Date: Mon, 16 Jul 2007 15:17:25 +0200
- To: public-html <public-html@w3.org>
(This is part of my detailed review of the Document Object Model section.) The spec says in reflecting attributes: If a reflecting DOM attribute is a floating point number type (float) and the content attribute is defined to contain a time offset, then the content attribute must be parsed according to the rules for parsing time ofsets first. If that fails, or if the attribute is absent, the default value must be returned instead, or the not-a-number value (NaN) if there is no default value. On setting, the given value must be converted to a string using the time offset serialisation rules, and that string must be used as the new content attribute value. I can't see any attributes that are of type float and are defined to contain a time offset. The attributes that contain a time offset are DOMTimeStamp, AFAICT. Shouldn't the above paragraph talk about DOMTimeStamp instead? (If not, it is not defined what should happen with attributes that are of type DOMTimeStamp, like HTMLTimeElement.date.) In any case, it is not defined what should happen with attributes that are of type float but don't contain a time offset (like HTMLProgressElement.value). -- Simon Pieters Opera Software
Received on Monday, 16 July 2007 13:17:34 UTC