[html5] r2608 - [e] (0) terminology consistency fixes
whatwg at whatwg.org
whatwg at whatwg.org
Mon Dec 29 02:43:55 PST 2008
Author: ianh
Date: 2008-12-29 02:43:54 -0800 (Mon, 29 Dec 2008)
New Revision: 2608
Modified:
index
source
Log:
[e] (0) terminology consistency fixes
Modified: index
===================================================================
--- index 2008-12-29 09:59:45 UTC (rev 2607)
+++ index 2008-12-29 10:43:54 UTC (rev 2608)
@@ -224,7 +224,7 @@
<li><a href=#boolean-attributes><span class=secno>2.4.2 </span>Boolean attributes</a></li>
<li><a href=#numbers><span class=secno>2.4.3 </span>Numbers</a>
<ol>
- <li><a href=#unsigned-integers><span class=secno>2.4.3.1 </span>Unsigned integers</a></li>
+ <li><a href=#non-negative-integers><span class=secno>2.4.3.1 </span>Non-negative integers</a></li>
<li><a href=#signed-integers><span class=secno>2.4.3.2 </span>Signed integers</a></li>
<li><a href=#real-numbers><span class=secno>2.4.3.3 </span>Real numbers</a></li>
<li><a href=#ratios><span class=secno>2.4.3.4 </span>Ratios</a></li>
@@ -2082,7 +2082,7 @@
<h4 id=numbers><span class=secno>2.4.3 </span>Numbers</h4>
- <h5 id=unsigned-integers><span class=secno>2.4.3.1 </span>Unsigned integers</h5>
+ <h5 id=non-negative-integers><span class=secno>2.4.3.1 </span>Non-negative integers</h5>
<p>A string is a <dfn id=valid-non-negative-integer>valid non-negative integer</dfn> if it
consists of one of more characters in the range U+0030 DIGIT ZERO
@@ -2142,7 +2142,8 @@
character.</p>
<p>The <dfn id=rules-for-parsing-integers>rules for parsing integers</dfn> are similar to the
- rules for non-negative integers, and are as given in the following
+ <a href=#rules-for-parsing-non-negative-integers title="rules for parsing non-negative integers">rules for
+ non-negative integers</a>, and are as given in the following
algorithm. When invoked, the steps must be followed in the order
given, aborting at the first step that returns a value. This
algorithm will either return an integer or an error. Leading spaces
@@ -2477,10 +2478,9 @@
</ol><h5 id=percentages-and-dimensions><span class=secno>2.4.3.5 </span>Percentages and dimensions</h5>
- <p class=XXX><dfn id=valid-positive-non-zero-integers>valid positive non-zero integers</dfn>
- <dfn id=rules-for-parsing-dimension-values>rules for parsing dimension values</dfn> (only used by
- height/width on img, embed, object — lengths in css pixels or
- percentages)</p>
+ <p class=XXX><dfn id=rules-for-parsing-dimension-values>rules for parsing dimension values</dfn> (only
+ used by height/width on img, embed, object — lengths in css
+ pixels or percentages)</p>
@@ -5163,31 +5163,30 @@
<p>If a reflecting DOM attribute is an <em>unsigned</em> integer
type (<code>unsigned long</code>) then, on getting, the content
- attribute must be parsed according to <a href=#rules-for-parsing-non-negative-integers title="rules for parsing
- non-negative integers">the rules for parsing unsigned
- integers</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 if there is
- no default value. On setting, the given value must be converted to
- the shortest possible string representing the number as a
- <a href=#valid-non-negative-integer>valid non-negative integer</a> in base ten and then that
- string must be used as the new content attribute value.</p>
+ attribute must be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing
+ non-negative integers</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 if there is no default value. On setting, the given
+ value must be converted to the shortest possible string representing
+ the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a> in base ten
+ and then that string must be used as the new content attribute
+ value.</p>
<p>If a reflecting DOM attribute is an unsigned integer type
(<code>unsigned long</code>) that is <dfn id=limited-to-only-positive-non-zero-numbers>limited to only positive
non-zero numbers</dfn>, then the behavior is similar to the previous
case, but zero is not allowed. On getting, the content attribute
- must first be parsed according to <a href=#rules-for-parsing-non-negative-integers title="rules for parsing
- non-negative integers">the rules for parsing unsigned
- integers</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 1 if there is
- no default value. On setting, if the value is zero, the user agent
- must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
- given value must be converted to the shortest possible string
- representing the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a>
- in base ten and then that string must be used as the new content
- attribute value.</p>
+ must first be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing
+ non-negative integers</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 1 if there is no default value. On setting, if the value
+ is zero, the user agent must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code>
+ exception. Otherwise, the given value must be converted to the
+ shortest possible string representing the number as a <a href=#valid-non-negative-integer>valid
+ non-negative integer</a> in base ten and then that string must be
+ used as the new content attribute value.</p>
<p>If a reflecting DOM attribute is a floating point number type
(<code>float</code>) and it doesn't fall into one of the earlier
@@ -21792,7 +21791,8 @@
of the visual content of the element (the width and height
respectively, relative to the nominal direction of the output
medium), in CSS pixels. The attributes, if specified, must have
- values that are <a href=#valid-positive-non-zero-integers>valid positive non-zero integers</a>.</p>
+ values that are <a href=#valid-non-negative-integer title="valid non-negative integer">valid
+ non-negative integers</a> greater than zero.</p>
<p>The specified dimensions given may differ from the dimensions
specified in the resource itself, since the resource may have a
Modified: source
===================================================================
--- source 2008-12-29 09:59:45 UTC (rev 2607)
+++ source 2008-12-29 10:43:54 UTC (rev 2608)
@@ -1157,7 +1157,7 @@
<h4>Numbers</h4>
- <h5>Unsigned integers</h5>
+ <h5>Non-negative integers</h5>
<p>A string is a <dfn>valid non-negative integer</dfn> if it
consists of one of more characters in the range U+0030 DIGIT ZERO
@@ -1230,7 +1230,8 @@
character.</p>
<p>The <dfn>rules for parsing integers</dfn> are similar to the
- rules for non-negative integers, and are as given in the following
+ <span title="rules for parsing non-negative integers">rules for
+ non-negative integers</span>, and are as given in the following
algorithm. When invoked, the steps must be followed in the order
given, aborting at the first step that returns a value. This
algorithm will either return an integer or an error. Leading spaces
@@ -1665,10 +1666,9 @@
<h5 id="percentages-and-dimensions">Percentages and dimensions</h5>
- <p class="XXX"><dfn>valid positive non-zero integers</dfn>
- <dfn>rules for parsing dimension values</dfn> (only used by
- height/width on img, embed, object — lengths in css pixels or
- percentages)</p>
+ <p class="XXX"><dfn>rules for parsing dimension values</dfn> (only
+ used by height/width on img, embed, object — lengths in css
+ pixels or percentages)</p>
@@ -5000,31 +5000,30 @@
<p>If a reflecting DOM attribute is an <em>unsigned</em> integer
type (<code>unsigned long</code>) then, on getting, the content
- attribute must be parsed according to <span title="rules for parsing
- non-negative integers">the rules for parsing unsigned
- integers</span>, 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 if there is
- no default value. On setting, the given value must be converted to
- the shortest possible string representing the number as a
- <span>valid non-negative integer</span> in base ten and then that
- string must be used as the new content attribute value.</p>
+ attribute must be parsed according to <span>rules for parsing
+ non-negative integers</span>, 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 if there is no default value. On setting, the given
+ value must be converted to the shortest possible string representing
+ the number as a <span>valid non-negative integer</span> in base ten
+ and then that string must be used as the new content attribute
+ value.</p>
<p>If a reflecting DOM attribute is an unsigned integer type
(<code>unsigned long</code>) that is <dfn>limited to only positive
non-zero numbers</dfn>, then the behavior is similar to the previous
case, but zero is not allowed. On getting, the content attribute
- must first be parsed according to <span title="rules for parsing
- non-negative integers">the rules for parsing unsigned
- integers</span>, 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 1 if there is
- no default value. On setting, if the value is zero, the user agent
- must fire an <code>INDEX_SIZE_ERR</code> exception. Otherwise, the
- given value must be converted to the shortest possible string
- representing the number as a <span>valid non-negative integer</span>
- in base ten and then that string must be used as the new content
- attribute value.</p>
+ must first be parsed according to <span>rules for parsing
+ non-negative integers</span>, 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 1 if there is no default value. On setting, if the value
+ is zero, the user agent must fire an <code>INDEX_SIZE_ERR</code>
+ exception. Otherwise, the given value must be converted to the
+ shortest possible string representing the number as a <span>valid
+ non-negative integer</span> in base ten and then that string must be
+ used as the new content attribute value.</p>
<p>If a reflecting DOM attribute is a floating point number type
(<code>float</code>) and it doesn't fall into one of the earlier
@@ -24047,7 +24046,8 @@
of the visual content of the element (the width and height
respectively, relative to the nominal direction of the output
medium), in CSS pixels. The attributes, if specified, must have
- values that are <span>valid positive non-zero integers</span>.</p>
+ values that are <span title="valid non-negative integer">valid
+ non-negative integers</span> greater than zero.</p>
<p>The specified dimensions given may differ from the dimensions
specified in the resource itself, since the resource may have a
More information about the Commit-Watchers
mailing list