Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[giow] (2) unsigned long range - extend fix in r5472 to cover also th…
…ose unsigned long attributes limited to non-zero values.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10352

git-svn-id: http://svn.whatwg.org/webapps@5494 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Sep 25, 2010
1 parent 41c4801 commit 87831ad
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 12 deletions.
8 changes: 4 additions & 4 deletions complete.html
Expand Up @@ -6631,16 +6631,16 @@ <h4 id=reflecting-content-attributes-in-idl-attributes><span class=secno>2.7.1 <
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
Expand Down
8 changes: 4 additions & 4 deletions index
Expand Up @@ -6608,16 +6608,16 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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
Expand Down
8 changes: 4 additions & 4 deletions source
Expand Up @@ -6286,16 +6286,16 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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
Expand Down

0 comments on commit 87831ad

Please sign in to comment.