Skip to content

Commit

Permalink
[e] (0) Clarify that Date objects can represent NaN values.
Browse files Browse the repository at this point in the history 
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=16626
Affected topics: DOM APIs

git-svn-id: http://svn.whatwg.org/webapps@7382 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Sep 20, 2012
1 parent 6b52e38 commit 9517fb6
Show file tree
Hide file tree
Showing 3 changed files with 29 additions and 20 deletions.
17 changes: 10 additions & 7 deletions complete.html
View file
Expand Up @@ -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 &mdash; Last Updated 19 September 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; 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>
Expand Down Expand Up @@ -4033,18 +4033,21 @@ <h4 id=dependencies><span class=secno>2.2.2 </span>Dependencies</h4>
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>

Expand Down
17 changes: 10 additions & 7 deletions index
View file
Expand Up @@ -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 &mdash; Last Updated 19 September 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; 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>
Expand Down Expand Up @@ -4033,18 +4033,21 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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>

Expand Down
15 changes: 9 additions & 6 deletions source
View file
Expand Up @@ -2962,18 +2962,21 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
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>

Expand Down

0 comments on commit 9517fb6

Please sign in to comment.