- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 11 Jun 2012 23:07:21 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv26795
Modified Files:
Overview.html
Log Message:
Update to take into account WebIDL's 'double' vs 'unrestricted double' change. (whatwg r7129)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5680
retrieving revision 1.5681
diff -u -d -r1.5680 -r1.5681
--- Overview.html 11 Jun 2012 20:53:36 -0000 1.5680
+++ Overview.html 11 Jun 2012 23:07:17 -0000 1.5681
@@ -3831,16 +3831,6 @@
characters</dfn> is similarly that defined in the Web IDL
specification.</p>
- <p id="float-nan">Except where otherwise specified, if an IDL
- attribute that is a floating point number type (<code title="">double</code>) is assigned an Infinity or Not-a-Number
- (NaN) value, a <code><a href="#notsupportederror">NotSupportedError</a></code> exception must be
- thrown.</p>
-
- <p>Except where otherwise specified, if a method with an argument
- that is a floating point number type (<code title="">double</code>)
- is passed an Infinity or Not-a-Number (NaN) value, a
- <code><a href="#notsupportederror">NotSupportedError</a></code> exception must be thrown.</p>
-
<p>When this specification requires a user agent to <dfn id="create-a-date-object">create a
<code>Date</code> object</dfn> representing a particular time, the
milliseconds component of that time, if any, must be truncated to
@@ -8394,35 +8384,36 @@
value.</p>
<p>If a reflecting IDL attribute has a floating point number type
- (<code>double</code>), then, on getting, the content attribute must
- be parsed 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 <a href="#best-representation-of-the-number-as-a-floating-point-number">best representation of the number as a
- floating point number</a> and then that string must be used as
- the new content attribute value.</p>
-
- <p>If a reflecting IDL attribute has a floating point number type
- (<code>double</code>) that is <dfn id="limited-to-numbers-greater-than-zero">limited to numbers greater than
- zero</dfn>, then the behavior is similar to the previous case, but
- zero and negative values are not allowed. On getting, the content
- attribute must be parsed 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 and
- the value is greater than 0.0, 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.0 if there is no default value. On setting, if the
- value is less than or equal to zero, then the value must be ignored.
- Otherwise, the given value must be converted to the <a href="#best-representation-of-the-number-as-a-floating-point-number">best
+ (<code>double</code> or <code>unrestricted double</code>), then, on
+ getting, the content attribute must be parsed 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 <a href="#best-representation-of-the-number-as-a-floating-point-number">best
representation of the number as a floating point number</a> and
then that string must be used as the new content attribute
value.</p>
+ <p>If a reflecting IDL attribute has a floating point number type
+ (<code>double</code> or <code>unrestricted double</code>) that is
+ <dfn id="limited-to-numbers-greater-than-zero">limited to numbers greater than zero</dfn>, then the behavior
+ is similar to the previous case, but zero and negative values are
+ not allowed. On getting, the content attribute must be parsed
+ 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 and the value is greater
+ than 0.0, 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.0 if
+ there is no default value. On setting, if the value is less than or
+ equal to zero, then the value must be ignored. Otherwise, the given
+ value must be converted to the <a href="#best-representation-of-the-number-as-a-floating-point-number">best representation of the
+ number as a floating point number</a> and then that string must
+ be used as the new content attribute value.</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>
+ throw an exception on setting, as defined in the Web IDL
+ specification. <a href="#refsWEBIDL">[WEBIDL]</a></p>
<p>If a reflecting IDL attribute has the type
<code><a href="#domtokenlist">DOMTokenList</a></code> or <code><a href="#domsettabletokenlist">DOMSettableTokenList</a></code>, then
@@ -26384,7 +26375,7 @@
// playback state
attribute double <a href="#dom-media-currenttime" title="dom-media-currentTime">currentTime</a>;
- readonly attribute double <a href="#dom-media-duration" title="dom-media-duration">duration</a>;
+ readonly attribute unrestricted double <a href="#dom-media-duration" title="dom-media-duration">duration</a>;
readonly attribute <span>Date</span> <a href="#dom-media-startdate" title="dom-media-startDate">startDate</a>;
readonly attribute boolean <a href="#dom-media-paused" title="dom-media-paused">paused</a>;
attribute double <a href="#dom-media-defaultplaybackrate" title="dom-media-defaultPlaybackRate">defaultPlaybackRate</a>;
@@ -29676,7 +29667,7 @@
readonly attribute <a href="#timeranges">TimeRanges</a> <a href="#dom-mediacontroller-buffered" title="dom-MediaController-buffered">buffered</a>;
readonly attribute <a href="#timeranges">TimeRanges</a> <a href="#dom-mediacontroller-seekable" title="dom-MediaController-seekable">seekable</a>;
- readonly attribute double <a href="#dom-mediacontroller-duration" title="dom-MediaController-duration">duration</a>;
+ readonly attribute unrestricted double <a href="#dom-mediacontroller-duration" title="dom-MediaController-duration">duration</a>;
attribute double <a href="#dom-mediacontroller-currenttime" title="dom-MediaController-currentTime">currentTime</a>;
readonly attribute boolean <a href="#dom-mediacontroller-paused" title="dom-MediaController-paused">paused</a>;
@@ -38033,7 +38024,7 @@
attribute DOMString <a href="#dom-input-defaultvalue" title="dom-input-defaultValue">defaultValue</a>;
attribute DOMString <a href="#dom-input-value" title="dom-input-value">value</a>;
attribute <span>Date</span>? <a href="#dom-input-valueasdate" title="dom-input-valueAsDate">valueAsDate</a>;
- attribute double <a href="#dom-input-valueasnumber" title="dom-input-valueAsNumber">valueAsNumber</a>;
+ attribute unrestricted double <a href="#dom-input-valueasnumber" title="dom-input-valueAsNumber">valueAsNumber</a>;
attribute unsigned long <a href="#dom-input-width" title="dom-input-width">width</a>;
void <a href="#dom-input-stepup" title="dom-input-stepUp">stepUp</a>(optional long n);
Received on Monday, 11 June 2012 23:07:24 UTC