html5/spec Overview.html,1.2725,1.2726

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv30673

Modified Files:
	Overview.html 
Log Message:
Clean up some of the conventions around Infinity and NaN. (whatwg r3528)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2725
retrieving revision 1.2726
diff -u -d -r1.2725 -r1.2726
--- Overview.html	3 Aug 2009 07:00:44 -0000	1.2725
+++ Overview.html	3 Aug 2009 07:16:26 -0000	1.2726
@@ -1921,14 +1921,14 @@
     required for conforming IDL fragments, as described in the Web IDL
     specification. <a href="#references">[WEBIDL]</a></p>
 
-    <p>Unless otherwise specified, if a DOM attribute that is a
-    floating point number type (<code title="">float</code>) is
-    assigned an Infinity or Not-a-Number value, a
+    <p id="float-nan">Unless otherwise specified, if a DOM attribute
+    that is a floating point number type (<code title="">float</code>)
+    is assigned an Infinity or Not-a-Number (NaN) value, a
     <code><a href="#not_supported_err">NOT_SUPPORTED_ERR</a></code> exception must be raised.</p>
 
     <p>Unless otherwise specified, if a method with an argument that
     is a floating point number type (<code title="">float</code>) is
-    passed an Infinity or Not-a-Number value, a
+    passed an Infinity or Not-a-Number (NaN) value, a
     <code><a href="#not_supported_err">NOT_SUPPORTED_ERR</a></code> exception must be raised.</p>
 
    </dd>
@@ -2309,7 +2309,8 @@
   between the E and the number and the number is not zero, or else
   ignoring a U+002B PLUS SIGN ("+") character between the E and the
   number if there is one). If there is no E, then the exponent is
-  treated as zero.<p class="note">The values &plusmn;Infinity and NaN are not <a href="#valid-floating-point-number" title="valid floating point number">valid floating point
+  treated as zero.<p class="note">The Infinity and Not-a-Number (NaN) values are not
+  <a href="#valid-floating-point-number" title="valid floating point number">valid floating point
   numbers</a>.<div class="impl">
 
   <p>The <dfn id="best-representation-of-the-floating-point-number">best representation of the floating point number</dfn>
@@ -4790,8 +4791,9 @@
   of the floating point number</a> and then that string must be
   used as the new content attribute value.</p>
 
-  <p class="note">The values &plusmn;Infinity and NaN throw an
-  exception on setting, as defined by Web IDL. <a href="#references">[WEBIDL]</a></p>
+  <p class="note">The values Infinity and Not-a-Number (NaN) values
+  throw an exception on setting, as <a href="#float-nan">defined
+  earlier</a>.</p>
 
   <p>If a reflecting DOM attribute is of the type
   <code><a href="#domtokenlist-0">DOMTokenList</a></code> or <code><a href="#domsettabletokenlist-0">DOMSettableTokenList</a></code>, then
@@ -20568,9 +20570,9 @@
   before they are composited onto the canvas. The value must be in the
   range from 0.0 (fully transparent) to 1.0 (no additional
   transparency). If an attempt is made to set the attribute to a value
-  outside this range (including Infinity and NaN values), the
-  attribute must retain its previous value. When the context is
-  created, the <code title="dom-context-2d-globalAlpha"><a href="#dom-context-2d-globalalpha">globalAlpha</a></code> attribute must
+  outside this range, including Infinity and Not-a-Number (NaN)
+  values, the attribute must retain its previous value. When the
+  context is created, the <code title="dom-context-2d-globalAlpha"><a href="#dom-context-2d-globalalpha">globalAlpha</a></code> attribute must
   initially have the value 1.0.</p>
 
   <p>The <dfn id="dom-context-2d-globalcompositeoperation" title="dom-context-2d-globalCompositeOperation"><code>globalCompositeOperation</code></dfn>
@@ -34152,11 +34154,11 @@
 
   <p>Where the above requirements say that a value is to be a number,
   the user agent must first apply the ToNumber() conversion operator
-  to the value, and then verify that the result is neither the
-  not-a-number NaN value nor an infinite value. If this result is
-  indeed acceptable (i.e. finite), the user agent must use the result
-  in the rest of the algorithm as if it had that had been the value
-  passed to the method. <a href="#references">[ECMA262]</a></p>
+  to the value, and then verify that the result is neither an Infinity
+  value nor a Not-a-Number (NaN) value. If this result is indeed
+  acceptable (i.e. finite), the user agent must use the result in the
+  rest of the algorithm as if it had that had been the value passed to
+  the method. <a href="#references">[ECMA262]</a></p>
 
   <p>Where the above requirements say that a value is to be an
   integer, the user agent must first apply the ToNumber() conversion
@@ -43481,9 +43483,8 @@
    <li><p>Apply the ToNumber() conversion operator to <var title="">timeout</var>, and let <var title="">timeout</var> be the
    result.</li>
 
-   <li><p>If <var title="">timeout</var> is not a number (NaN), not
-   finite (Infinity), or negative, let <var title="">timeout</var> be
-   zero.</li>
+   <li><p>If <var title="">timeout</var> is an Infinity value, a
+   Not-a-Number (NaN) value, or negative, let <var title="">timeout</var> be zero.</li>
 
    <li><p>Round <var title="">timeout</var> down to the nearest
    integer, and let <var title="">timeout</var> be the

Received on Monday, 3 August 2009 07:16:39 UTC