[html5] r7382 - [e] (0) Clarify that Date objects can represent NaN values. Fixing https://www.w [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Sep 19 23:22:32 PDT 2012
Author: ianh
Date: 2012-09-19 23:22:31 -0700 (Wed, 19 Sep 2012)
New Revision: 7382
Modified:
complete.html
index
source
Log:
[e] (0) Clarify that Date objects can represent NaN values.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=16626
Affected topics: DOM APIs
Modified: complete.html
===================================================================
--- complete.html 2012-09-19 23:07:28 UTC (rev 7381)
+++ complete.html 2012-09-20 06:22:31 UTC (rev 7382)
@@ -246,7 +246,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 19 September 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 20 September 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -4033,18 +4033,21 @@
specification.</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
- an integer and the time value of the newly created
- <code>Date</code> object must represent the time after that
- truncation.</p>
+ <code>Date</code> object</dfn> representing a particular time
+ (which could be the special value Not-a-Number), the milliseconds
+ component of that time, if any, must be truncated to an integer
+ and the time value of the newly created <code>Date</code> object
+ must represent the time after that truncation.</p>
<p class=example>For instance, given the time 23045 millionths
of a second after 01:00 UTC on January 1st 2000, i.e. the time
2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
created representing that time would represent the same time as
that created representing the time 2000-01-01T00:00:00.023Z, 45
- millionths earlier.</p>
+ millionths earlier. If the given time is NaN, then the result is a
+ <code>Date</code> object that represents a time value NaN
+ (indicating that the object does not represent a specific instant
+ of time).</p>
</dd>
Modified: index
===================================================================
--- index 2012-09-19 23:07:28 UTC (rev 7381)
+++ index 2012-09-20 06:22:31 UTC (rev 7382)
@@ -246,7 +246,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 19 September 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 20 September 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -4033,18 +4033,21 @@
specification.</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
- an integer and the time value of the newly created
- <code>Date</code> object must represent the time after that
- truncation.</p>
+ <code>Date</code> object</dfn> representing a particular time
+ (which could be the special value Not-a-Number), the milliseconds
+ component of that time, if any, must be truncated to an integer
+ and the time value of the newly created <code>Date</code> object
+ must represent the time after that truncation.</p>
<p class=example>For instance, given the time 23045 millionths
of a second after 01:00 UTC on January 1st 2000, i.e. the time
2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
created representing that time would represent the same time as
that created representing the time 2000-01-01T00:00:00.023Z, 45
- millionths earlier.</p>
+ millionths earlier. If the given time is NaN, then the result is a
+ <code>Date</code> object that represents a time value NaN
+ (indicating that the object does not represent a specific instant
+ of time).</p>
</dd>
Modified: source
===================================================================
--- source 2012-09-19 23:07:28 UTC (rev 7381)
+++ source 2012-09-20 06:22:31 UTC (rev 7382)
@@ -2962,18 +2962,21 @@
specification.</p>
<p>When this specification requires a user agent to <dfn>create a
- <code>Date</code> object</dfn> representing a particular time, the
- milliseconds component of that time, if any, must be truncated to
- an integer and the time value of the newly created
- <code>Date</code> object must represent the time after that
- truncation.</p>
+ <code>Date</code> object</dfn> representing a particular time
+ (which could be the special value Not-a-Number), the milliseconds
+ component of that time, if any, must be truncated to an integer
+ and the time value of the newly created <code>Date</code> object
+ must represent the time after that truncation.</p>
<p class="example">For instance, given the time 23045 millionths
of a second after 01:00 UTC on January 1st 2000, i.e. the time
2000-01-01T00:00:00.023045Z, then the <code>Date</code> object
created representing that time would represent the same time as
that created representing the time 2000-01-01T00:00:00.023Z, 45
- millionths earlier.</p>
+ millionths earlier. If the given time is NaN, then the result is a
+ <code>Date</code> object that represents a time value NaN
+ (indicating that the object does not represent a specific instant
+ of time).</p>
</dd>
More information about the Commit-Watchers
mailing list