- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 29 Jul 2009 07:51:32 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/markup
In directory hutz:/tmp/cvs-serv27016
Modified Files:
meter.html progress.html spec.html
Log Message:
further streamlining of <meter> documentation
Index: progress.html
===================================================================
RCS file: /sources/public/html5/markup/progress.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- progress.html 29 Jul 2009 07:19:23 -0000 1.11
+++ progress.html 29 Jul 2009 07:51:29 -0000 1.12
@@ -72,16 +72,6 @@
</div>
- <div class="no-number no-toc" id="progress-details">
- <h2 class="element-subhead">Details <a class="hash" href="#progress-details">#</a></h2>
- <p>The progress is either indeterminate, indicating that
- progress is being made but that it is not clear how much more
- work remains to be done before the task is complete (for
- example, because the task is waiting for a remote host to
- respond), or the progress is a number in the range zero to a
- maximum, giving the fraction of work that has so far been
- completed.</p>
- </div>
<div class="no-number no-toc" id="progress-context">
<h2 class="element-subhead">Permitted contexts <a class="hash" href="#progress-context">#</a></h2>
<ul>
Index: meter.html
===================================================================
RCS file: /sources/public/html5/markup/meter.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- meter.html 29 Jul 2009 07:42:42 -0000 1.12
+++ meter.html 29 Jul 2009 07:51:29 -0000 1.13
@@ -43,66 +43,35 @@
<dt><a class="attribute-name" id="meter.attrs.value" title="meter.attrs.value" href="meter.html#meter.attrs.value">value</a><span class="attr-values"> =
<a class="ref" href="datatypes.html#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>Specifies the value to have the gauge indicate as the
- “measured” value.</dd>
+ <dd>The “measured” value shown by meter.</dd>
<dt><a class="attribute-name" id="meter.attrs.min" title="meter.attrs.min" href="meter.html#meter.attrs.min">min</a><span class="attr-values"> =
<a class="ref" href="datatypes.html#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The lower bound of the range; the <code>max</code>
- attribute specifies the upper bound. The
- <code>value</code> attribute specifies the value to have
- the gauge indicate as the “measured” value.</dd>
+ <dd>The lower bound of the range for the meter.</dd>
<dt><a class="attribute-name" id="meter.attrs.low" title="meter.attrs.low" href="meter.html#meter.attrs.low">low</a><span class="attr-values"> =
<a class="ref" href="datatypes.html#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The other three attributes can be used to segment the gauge's range into
- "low", "medium", and "high" parts, and to indicate which part of the gauge
- is the "optimum" part. The <code>low</code> attribute specifies the range
- that is considered to be the "low" part, and the
- <code>high</code> attribute specifies the
- range that is considered to be the "high" part. The
- <code>optimum</code> attribute
- gives the
- position that is "optimum"; if that is higher than the "high" value then
- this indicates that the higher the value, the better; if it's lower than
- the "low" mark then it indicates that lower values are better, and
- naturally if it is in between then it indicates that neither high nor low
- values are good.</dd>
+ <dd>The point that marks the upper boundary of the “low”
+ segment of the meter.</dd>
<dt><a class="attribute-name" id="meter.attrs.high" title="meter.attrs.high" href="meter.html#meter.attrs.high">high</a><span class="attr-values"> =
<a class="ref" href="datatypes.html#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The other three attributes can be used to segment the gauge's range into
- "low", "medium", and "high" parts, and to indicate which part of the gauge
- is the "optimum" part. The <code>low</code> attribute specifies the range
- that is considered to be the "low" part, and the <code>high</code> attribute specifies the
- range that is considered to be the "high" part. The <code>optimum</code> attribute gives the
- position that is "optimum"; if that is higher than the "high" value then
- this indicates that the higher the value, the better; if it's lower than
- the "low" mark then it indicates that lower values are better, and
- naturally if it is in between then it indicates that neither high nor low
- values are good.</dd>
+ <dd>The point that marks the lower boundary of the “high”
+ segment of the meter.</dd>
<dt><a class="attribute-name" id="meter.attrs.max" title="meter.attrs.max" href="meter.html#meter.attrs.max">max</a><span class="attr-values"> =
<a class="ref" href="datatypes.html#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>Specifies the upper bound.</dd>
+ <dd>The upper bound of the range for the meter.</dd>
<dt><a class="attribute-name" id="meter.attrs.optimum" title="meter.attrs.optimum" href="meter.html#meter.attrs.optimum">optimum</a><span class="attr-values"> =
<a class="ref" href="datatypes.html#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The other three attributes can be used to segment the gauge's range into
- "low", "medium", and "high" parts, and to indicate which part of the gauge
- is the "optimum" part. The <code>low</code> attribute specifies the range
- that is considered to be the "low" part, and the <code>high</code> attribute specifies the
- range that is considered to be the "high" part. The <code>optimum</code> attribute gives the
- position that is "optimum"; if that is higher than the "high" value then
- this indicates that the higher the value, the better; if it's lower than
- the "low" mark then it indicates that lower values are better, and
- naturally if it is in between then it indicates that neither high nor low
- values are good.</dd>
+ <dd>The point that marks the “optimum” position for the
+ meter.</dd>
</dl></div>
Index: spec.html
===================================================================
RCS file: /sources/public/html5/markup/spec.html,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -d -r1.65 -r1.66
--- spec.html 29 Jul 2009 07:42:42 -0000 1.65
+++ spec.html 29 Jul 2009 07:51:29 -0000 1.66
@@ -10775,71 +10775,40 @@
<a class="attribute-name" id="meter.attrs.value" title="meter.attrs.value" href="#meter.attrs.value">value</a><span class="attr-values"> =
<a class="ref" href="#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>Specifies the value to have the gauge indicate as the
- “measured” value.</dd>
+ <dd>The “measured” value shown by meter.</dd>
<dt>
<a class="attribute-name" id="meter.attrs.min" title="meter.attrs.min" href="#meter.attrs.min">min</a><span class="attr-values"> =
<a class="ref" href="#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The lower bound of the range; the <code>max</code>
- attribute specifies the upper bound. The
- <code>value</code> attribute specifies the value to have
- the gauge indicate as the “measured” value.</dd>
+ <dd>The lower bound of the range for the meter.</dd>
<dt>
<a class="attribute-name" id="meter.attrs.low" title="meter.attrs.low" href="#meter.attrs.low">low</a><span class="attr-values"> =
<a class="ref" href="#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The other three attributes can be used to segment the gauge's range into
- "low", "medium", and "high" parts, and to indicate which part of the gauge
- is the "optimum" part. The <code>low</code> attribute specifies the range
- that is considered to be the "low" part, and the
- <code>high</code> attribute specifies the
- range that is considered to be the "high" part. The
- <code>optimum</code> attribute
- gives the
- position that is "optimum"; if that is higher than the "high" value then
- this indicates that the higher the value, the better; if it's lower than
- the "low" mark then it indicates that lower values are better, and
- naturally if it is in between then it indicates that neither high nor low
- values are good.</dd>
+ <dd>The point that marks the upper boundary of the “low”
+ segment of the meter.</dd>
<dt>
<a class="attribute-name" id="meter.attrs.high" title="meter.attrs.high" href="#meter.attrs.high">high</a><span class="attr-values"> =
<a class="ref" href="#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The other three attributes can be used to segment the gauge's range into
- "low", "medium", and "high" parts, and to indicate which part of the gauge
- is the "optimum" part. The <code>low</code> attribute specifies the range
- that is considered to be the "low" part, and the <code>high</code> attribute specifies the
- range that is considered to be the "high" part. The <code>optimum</code> attribute gives the
- position that is "optimum"; if that is higher than the "high" value then
- this indicates that the higher the value, the better; if it's lower than
- the "low" mark then it indicates that lower values are better, and
- naturally if it is in between then it indicates that neither high nor low
- values are good.</dd>
+ <dd>The point that marks the lower boundary of the “high”
+ segment of the meter.</dd>
<dt>
<a class="attribute-name" id="meter.attrs.max" title="meter.attrs.max" href="#meter.attrs.max">max</a><span class="attr-values"> =
<a class="ref" href="#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>Specifies the upper bound.</dd>
+ <dd>The upper bound of the range for the meter.</dd>
<dt>
<a class="attribute-name" id="meter.attrs.optimum" title="meter.attrs.optimum" href="#meter.attrs.optimum">optimum</a><span class="attr-values"> =
<a class="ref" href="#common.data.float" title="common.data.float">float</a>
</span> </dt>
- <dd>The other three attributes can be used to segment the gauge's range into
- "low", "medium", and "high" parts, and to indicate which part of the gauge
- is the "optimum" part. The <code>low</code> attribute specifies the range
- that is considered to be the "low" part, and the <code>high</code> attribute specifies the
- range that is considered to be the "high" part. The <code>optimum</code> attribute gives the
- position that is "optimum"; if that is higher than the "high" value then
- this indicates that the higher the value, the better; if it's lower than
- the "low" mark then it indicates that lower values are better, and
- naturally if it is in between then it indicates that neither high nor low
- values are good.</dd>
+ <dd>The point that marks the “optimum” position for the
+ meter.</dd>
</dl>
</div>
@@ -11820,17 +11789,6 @@
</div>
- <div class="no-number no-toc" id="progress-details">
- <h2 class="element-subhead">Details <a class="hash" href="#progress-details">#</a>
-</h2>
- <p>The progress is either indeterminate, indicating that
- progress is being made but that it is not clear how much more
- work remains to be done before the task is complete (for
- example, because the task is waiting for a remote host to
- respond), or the progress is a number in the range zero to a
- maximum, giving the fraction of work that has so far been
- completed.</p>
- </div>
<div class="no-number no-toc" id="progress-context">
<h2 class="element-subhead">Permitted contexts <a class="hash" href="#progress-context">#</a>
</h2>
Received on Wednesday, 29 July 2009 07:51:40 UTC