- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 25 Feb 2011 08:46:52 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv3822
Modified Files:
common-microsyntaxes.html spec.html the-button-element.html
webappapis.html
Log Message:
typo (whatwg r5916)
[updated by splitter]
Index: the-button-element.html
===================================================================
RCS file: /sources/public/html5/spec/the-button-element.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -d -r1.50 -r1.51
--- the-button-element.html 18 Feb 2011 08:47:04 -0000 1.50
+++ the-button-element.html 25 Feb 2011 08:46:50 -0000 1.51
@@ -2087,14 +2087,19 @@
attribute must return −1. Otherwise, it must return the
result of dividing the <a href="#concept-progress-value" title="concept-progress-value">current value</a> by the <a href="#concept-progress-maximum" title="concept-progress-maximum">maximum value</a>.</p>
- <p>Similarly, if the progress bar is an indeterminate progress bar,
- then the <dfn id="dom-progress-value" title="dom-progress-value"><code>value</code></dfn>
- IDL attribute, on getting, must return −1. Otherwise, it must
- return the <a href="#concept-progress-value" title="concept-progress-value">current
- value</a>. On setting, the given value must be converted to the
- <a href="common-microsyntaxes.html#best-representation-of-the-number-as-a-floating-point-number">best representation of the number as a floating point
- number</a> and then the <code title="dom-progress-value"><a href="#dom-progress-value">value</a></code> content attribute must be
- set to that string.</p>
+ <p>If the progress bar is an indeterminate progress bar, then the
+ <dfn id="dom-progress-value" title="dom-progress-value"><code>value</code></dfn> IDL
+ attribute, on getting, must return 0. Otherwise, it must return the
+ <a href="#concept-progress-value" title="concept-progress-value">current value</a>. On
+ setting, the given value must be converted to the <a href="common-microsyntaxes.html#best-representation-of-the-number-as-a-floating-point-number">best
+ representation of the number as a floating point number</a> and
+ then the <code title="dom-progress-value"><a href="#dom-progress-value">value</a></code> content
+ attribute must be set to that string.</p>
+
+ <p class="note">Setting the <code title="dom-progress-value"><a href="#dom-progress-value">value</a></code> IDL attribute to itself when
+ the corresponding content attribute is absent would change the
+ progress bar from an indeterminate progress bar to a determinate
+ progress bar with no progress.</p>
<p>The <dfn id="dom-progress-max" title="dom-progress-max"><code>max</code></dfn> IDL
attribute must <a href="common-dom-interfaces.html#reflect">reflect</a> the content attribute of the
Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1390
retrieving revision 1.1391
diff -u -d -r1.1390 -r1.1391
--- spec.html 25 Feb 2011 07:46:37 -0000 1.1390
+++ spec.html 25 Feb 2011 08:46:50 -0000 1.1391
@@ -369,7 +369,7 @@
<a href="Overview.html">single page HTML</a>,
<a href="spec.html">multipage HTML</a>,
<a href="author/">web developer edition</a>.
-This is revision 1.4752.
+This is revision 1.4756.
</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2010 <a href="http://www.w3.org/"><abbr title="World Wide
Index: webappapis.html
===================================================================
RCS file: /sources/public/html5/spec/webappapis.html,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -d -r1.156 -r1.157
--- webappapis.html 18 Feb 2011 22:46:44 -0000 1.156
+++ webappapis.html 25 Feb 2011 08:46:50 -0000 1.157
@@ -1558,7 +1558,7 @@
interface (part of Web Workers).</p>
<p>The <dfn id="dom-windowbase64-btoa" title="dom-windowbase64-btoa"><code>btoa()</code></dfn>
- method must throw an <code><a href="common-dom-interfaces.html#invalid_character_err">INVALID_CHARACTER_ERR</a></code> exeption if
+ method must throw an <code><a href="common-dom-interfaces.html#invalid_character_err">INVALID_CHARACTER_ERR</a></code> exception if
the method's first argument contains any character whose code point
is greater than U+00FF. Otherwise, the user agent must convert that
argument to a sequence of octets whose <var title="">n</var>th octet
Index: common-microsyntaxes.html
===================================================================
RCS file: /sources/public/html5/spec/common-microsyntaxes.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- common-microsyntaxes.html 18 Feb 2011 08:46:48 -0000 1.35
+++ common-microsyntaxes.html 25 Feb 2011 08:46:50 -0000 1.36
@@ -767,7 +767,7 @@
</ol></li>
<li><p><i>Conversion</i>: Let <var title="">S</var> be the set of
- finite IEEE 754 single-precision floating point values except
+ finite IEEE 754 double-precision floating point values except
−0, but with two special values added: 2<sup title="">1024</sup> and −2<sup title="">1024</sup>.</p></li>
<li><p>Let <var title="">rounded-value</var> be the number in <var title="">S</var> that is closest to <var title="">value</var>,
@@ -1601,16 +1601,23 @@
</ol><p class="note">This format allows for time-zone offsets from -23:59
to +23:59. In practice, however, the range of offsets of actual time
zones is -12:00 to +14:00, and the minutes component of offsets of
- actual time zones is always either 00, 30, or 45.</p><div class="example">
+ actual time zones is always either 00, 30, or 45.</p><p>Times in dates before the formation of UTC in the mid twentieth
+ century must be expressed and interpreted in terms of UT1
+ (contemporary Earth solar time at the 0° longitude), not UTC
+ (the approximation of UT1 that ticks in SI seconds). Time before the
+ formation of time zones must be expressed and interpeted as UT1
+ times with explicit time zones that approximate the contemporary
+ difference between the appropriate local time and the time observed
+ at the location of Greenwich, London.</p><div class="example">
<p>The following are some examples of dates written as <a href="#valid-global-date-and-time-string" title="valid global date and time string">valid global date and
time strings</a>.</p>
<dl><dt>"<code>0037-12-13T00:00Z</code>"</dt>
- <dd>Midnight UTC on the birthday of Nero (the Roman Emperor). See
- below for further discussion on which date this actually
- corresponds to.</dd>
+ <dd>Midnight in areas using London time on the birthday of Nero
+ (the Roman Emperor). See below for further discussion on which
+ date this actually corresponds to.</dd>
<dt>"<code>1979-10-14T12:00:00.001-04:00</code>"</dt>
@@ -1631,21 +1638,27 @@
zero-padded. The date "37-12-13" would not be a valid date.</li>
<li>To unambiguously identify a moment in time prior to the
- introduction of the Gregorian calendar, the date has to be first
- converted to the Gregorian calendar from the calendar in use at
- the time (e.g. from the Julian calendar). The date of Nero's birth
- is the 15th of December 37, in the Julian Calendar, which is the
- 13th of December 37 in the proleptic Gregorian Calendar.</li> <!--
- This might not be true. I can't find a reference that gives his
- birthday with an explicit statement about the calendar being
- used. However, it seems unlikely that it would be given in the
- Gregorian calendar, so I assume sites use the Julian one. -->
+ introduction of the Gregorian calendar (insofar as moments in time
+ before the formation of UTC can be unambiguously identified), the
+ date has to be first converted to the Gregorian calendar from the
+ calendar in use at the time (e.g. from the Julian calendar). The
+ date of Nero's birth is the 15th of December 37, in the Julian
+ Calendar, which is the 13th of December 37 in the proleptic
+ Gregorian Calendar.</li> <!-- This might not be true. I can't find
+ a reference that gives his birthday with an explicit statement
+ about the calendar being used. However, it seems unlikely that it
+ would be given in the Gregorian calendar, so I assume sites use
+ the Julian one. -->
<li>The time and time-zone offset components are not optional.</li>
<li>Dates before the year one can't be represented as a datetime
in this version of HTML.</li>
+ <li>Times of specific events in ancient times are, at best,
+ approximations, since time was not well coordinated or measured
+ until relatively recent decades.</li>
+
<li>Time-zone offsets differ based on daylight savings time.</li>
</ul></div><div class="impl">
Received on Friday, 25 February 2011 08:46:54 UTC