- From: poot <cvsmail@w3.org>
- Date: Wed, 14 Jan 2009 17:53:32 +0900 (JST)
- To: public-html-diffs@w3.org
grammar (whatwg r2663) limited to only known values http://people.w3.org/mike/diffs/html5/spec/Overview.1.1833.html#limited-to-only-known-values limited to only positive non-zero numbers http://people.w3.org/mike/diffs/html5/spec/Overview.1.1833.html#limited-to-only-positive-non-zero-numbers http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1832&r2=1.1833&f=h http://html5.org/tools/web-apps-tracker?from=2662&to=2663 =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.1832 retrieving revision 1.1833 diff -u -d -r1.1832 -r1.1833 --- Overview.html 14 Jan 2009 08:47:01 -0000 1.1832 +++ Overview.html 14 Jan 2009 08:50:46 -0000 1.1833 @@ -4379,17 +4379,17 @@ true. (This corresponds to the rules for <a href=#boolean-attribute title="boolean attribute">boolean content attributes</a>.)<p>If a reflecting DOM attribute is a signed integer type (<code>long</code>) then, on getting, the content attribute must be - parsed according to <a href=#rules-for-parsing-integers title="rules for parsing integers">the - rules for parsing signed integers</a>, and if that is successful, - the resulting value must be returned. If, on the other hand, it - fails, or if the attribute is absent, then the default value must be - returned instead, or 0 if there is no default value. On setting, the - given value must be converted to the shortest possible string - representing the number as a <a href=#valid-integer>valid integer</a> in base ten - and then that string must be used as the new content attribute - value.<p>If a reflecting DOM attribute is an <em>unsigned</em> integer + parsed according to the <a href=#rules-for-parsing-integers title="rules for parsing + integers">rules for parsing signed integers</a>, and if that is + successful, the resulting value must be returned. If, on the other + hand, it fails, or if the attribute is absent, then the default + value must be returned instead, or 0 if there is no default + value. On setting, the given value must be converted to the shortest + possible string representing the number as a <a href=#valid-integer>valid + integer</a> in base ten and then that string must be used as the + new content attribute value.<p>If a reflecting DOM attribute is an <em>unsigned</em> integer type (<code>unsigned long</code>) then, on getting, the content - attribute must be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing + attribute must be parsed according to the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</a>, and if that is successful, the resulting value must be returned. If, on the other hand, it fails, or if the attribute is absent, the default value must be returned @@ -4401,7 +4401,7 @@ (<code>unsigned long</code>) that is <dfn id=limited-to-only-positive-non-zero-numbers>limited to only positive non-zero numbers</dfn>, then the behavior is similar to the previous case, but zero is not allowed. On getting, the content attribute - must first be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing + must first be parsed according to the <a href=#rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</a>, and if that is successful, the resulting value must be returned. If, on the other hand, it fails, or if the attribute is absent, the default value must be returned @@ -4413,15 +4413,14 @@ used as the new content attribute value.<p>If a reflecting DOM attribute is a floating point number type (<code>float</code>) and it doesn't fall into one of the earlier categories, then, on getting, the content attribute must be parsed - according to <a href=#rules-for-parsing-floating-point-number-values title="rules for parsing floating point number - values">the rules for parsing floating point number values</a>, - and if that is successful, the resulting value must be returned. If, - on the other hand, it fails, or if the attribute is absent, the - default value must be returned instead, or 0.0 if there is no - default value. On setting, the given value must be converted to the - shortest possible string representing the number as a <a href=#valid-floating-point-number>valid - floating point number</a> in base ten and then that string must - be used as the new content attribute value.<p>If a reflecting DOM attribute is of the type + according to the <a href=#rules-for-parsing-floating-point-number-values>rules for parsing floating point number + values</a>, and if that is successful, the resulting value must + be returned. If, on the other hand, it fails, or if the attribute is + absent, the default value must be returned instead, or 0.0 if there + is no default value. On setting, the given value must be converted + to the shortest possible string representing the number as a + <a href=#valid-floating-point-number>valid floating point number</a> in base ten and then that + string must be used as the new content attribute value.<p>If a reflecting DOM attribute is of the type <code><a href=#domtokenlist-0>DOMTokenList</a></code>, then on getting it must return a <code><a href=#domtokenlist-0>DOMTokenList</a></code> object whose underlying string is the element's corresponding content attribute. When the
Received on Wednesday, 14 January 2009 08:54:10 UTC