[html5] r5494 - [giow] (2) unsigned long range - extend fix in r5472 to cover also those unsigne [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-09-25 11:52:56 -0700 (Sat, 25 Sep 2010)
New Revision: 5494

Modified:
   complete.html
   index
   source
Log:
[giow] (2) unsigned long range - extend fix in r5472 to cover also those unsigned long attributes limited to non-zero values.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10352

Modified: complete.html
===================================================================
--- complete.html	2010-09-25 18:13:41 UTC (rev 5493)
+++ complete.html	2010-09-25 18:52:56 UTC (rev 5494)
@@ -6631,16 +6631,16 @@
   similar to the previous case, but zero is not allowed. On getting,
   the content attribute 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, and the value is in the range of the IDL attribute's
-  type, the resulting value must be returned. If, on the other hand,
-  it fails or returns an out of range value, or if the attribute is
+  successful, and the value is in the range 0 to 2147483647 inclusive,
+  the resulting value must be returned. If, on the other hand, it
+  fails or returns an out of range value, or if the attribute is
   absent, the default value must be returned instead, or 1 if there is
   no default value. On setting, if the value is zero, the user agent
   must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
   given value must be converted to the shortest possible string
   representing the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a>
   and then that string must be used as the new content attribute
-  value.</p>
+  value.</p> <!-- see previous paragraph for note about the range -->
 
   <p>If a reflecting IDL attribute is a floating point number type
   (<code>double</code>), then, on getting, the content attribute must

Modified: index
===================================================================
--- index	2010-09-25 18:13:41 UTC (rev 5493)
+++ index	2010-09-25 18:52:56 UTC (rev 5494)
@@ -6608,16 +6608,16 @@
   similar to the previous case, but zero is not allowed. On getting,
   the content attribute 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, and the value is in the range of the IDL attribute's
-  type, the resulting value must be returned. If, on the other hand,
-  it fails or returns an out of range value, or if the attribute is
+  successful, and the value is in the range 0 to 2147483647 inclusive,
+  the resulting value must be returned. If, on the other hand, it
+  fails or returns an out of range value, or if the attribute is
   absent, the default value must be returned instead, or 1 if there is
   no default value. On setting, if the value is zero, the user agent
   must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
   given value must be converted to the shortest possible string
   representing the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a>
   and then that string must be used as the new content attribute
-  value.</p>
+  value.</p> <!-- see previous paragraph for note about the range -->
 
   <p>If a reflecting IDL attribute is a floating point number type
   (<code>double</code>), then, on getting, the content attribute must

Modified: source
===================================================================
--- source	2010-09-25 18:13:41 UTC (rev 5493)
+++ source	2010-09-25 18:52:56 UTC (rev 5494)
@@ -6286,16 +6286,16 @@
   similar to the previous case, but zero is not allowed. On getting,
   the content attribute must first be parsed according to the
   <span>rules for parsing non-negative integers</span>, and if that is
-  successful, and the value is in the range of the IDL attribute's
-  type, the resulting value must be returned. If, on the other hand,
-  it fails or returns an out of range value, or if the attribute is
+  successful, and the value is in the range 0 to 2147483647 inclusive,
+  the resulting value must be returned. If, on the other hand, it
+  fails or returns an out of range value, or if the attribute is
   absent, the default value must be returned instead, or 1 if there is
   no default value. On setting, if the value is zero, the user agent
   must fire an <code>INDEX_SIZE_ERR</code> exception. Otherwise, the
   given value must be converted to the shortest possible string
   representing the number as a <span>valid non-negative integer</span>
   and then that string must be used as the new content attribute
-  value.</p>
+  value.</p> <!-- see previous paragraph for note about the range -->
 
   <p>If a reflecting IDL attribute is a floating point number type
   (<code>double</code>), then, on getting, the content attribute must