[html5] r5472 - [giow] (2) Match reality for reflection of unsigned long IDL attrs. Fixing http: [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-09-23 17:46:07 -0700 (Thu, 23 Sep 2010)
New Revision: 5472

Modified:
   complete.html
   index
   source
Log:
[giow] (2) Match reality for reflection of unsigned long IDL attrs.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10352

Modified: complete.html
===================================================================
--- complete.html	2010-09-23 22:44:34 UTC (rev 5471)
+++ complete.html	2010-09-24 00:46:07 UTC (rev 5472)
@@ -6608,14 +6608,18 @@
   type (<code>unsigned long</code>) then, on getting, the content
   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, 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 absent, 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-non-negative-integer>valid
-  non-negative integer</a> and then that string must be used as the
-  new content attribute value.</p>
+  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 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-non-negative-integer>valid non-negative
+  integer</a> and then that string must be used as the new content
+  attribute value.</p>
+  <!-- see http://www.w3.org/Bugs/Public/show_bug.cgi?id=10352 and
+  https://bugzilla.mozilla.org/show_bug.cgi?id=586118 for why the
+  range is clamped to 2147483647 rather the normal unsigned long
+  maximum value of 4294967295 -->
 
   <p>If a reflecting IDL attribute is an unsigned integer type
   (<code>unsigned long</code>) that is <dfn id=limited-to-only-non-negative-numbers-greater-than-zero>limited to only

Modified: index
===================================================================
--- index	2010-09-23 22:44:34 UTC (rev 5471)
+++ index	2010-09-24 00:46:07 UTC (rev 5472)
@@ -6585,14 +6585,18 @@
   type (<code>unsigned long</code>) then, on getting, the content
   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, 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 absent, 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-non-negative-integer>valid
-  non-negative integer</a> and then that string must be used as the
-  new content attribute value.</p>
+  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 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-non-negative-integer>valid non-negative
+  integer</a> and then that string must be used as the new content
+  attribute value.</p>
+  <!-- see http://www.w3.org/Bugs/Public/show_bug.cgi?id=10352 and
+  https://bugzilla.mozilla.org/show_bug.cgi?id=586118 for why the
+  range is clamped to 2147483647 rather the normal unsigned long
+  maximum value of 4294967295 -->
 
   <p>If a reflecting IDL attribute is an unsigned integer type
   (<code>unsigned long</code>) that is <dfn id=limited-to-only-non-negative-numbers-greater-than-zero>limited to only

Modified: source
===================================================================
--- source	2010-09-23 22:44:34 UTC (rev 5471)
+++ source	2010-09-24 00:46:07 UTC (rev 5472)
@@ -6265,14 +6265,18 @@
   type (<code>unsigned long</code>) then, on getting, the content
   attribute must 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 absent, 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 <span>valid
-  non-negative integer</span> and then that string must be used as the
-  new content attribute value.</p>
+  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 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 <span>valid non-negative
+  integer</span> and then that string must be used as the new content
+  attribute value.</p>
+  <!-- see http://www.w3.org/Bugs/Public/show_bug.cgi?id=10352 and
+  https://bugzilla.mozilla.org/show_bug.cgi?id=586118 for why the
+  range is clamped to 2147483647 rather the normal unsigned long
+  maximum value of 4294967295 -->
 
   <p>If a reflecting IDL attribute is an unsigned integer type
   (<code>unsigned long</code>) that is <dfn>limited to only