- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 14 Jul 2011 01:35:38 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-lists
In directory hutz:/tmp/cvs-serv13508
Modified Files:
Overview.html Overview.src.html
Log Message:
Bunch of editorial edits; nothing normatively important.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-lists/Overview.html,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -d -r1.67 -r1.68
--- Overview.html 9 Jul 2011 01:23:00 -0000 1.67
+++ Overview.html 14 Jul 2011 01:35:36 -0000 1.68
@@ -25,12 +25,12 @@
<h1>CSS Lists and Counters Module Level 3</h1>
- <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 9 July 2011</h2>
+ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 14 July 2011</h2>
<dl>
<dt>This version:
- <dd><!--<a href="http://www.w3.org/TR/2011/WD-css3-lists-20110709">http://www.w3.org/TR/2011/WD-css3-lists-20110709</a></dd>-->
+ <dd><!--<a href="http://www.w3.org/TR/2011/WD-css3-lists-20110714">http://www.w3.org/TR/2011/WD-css3-lists-20110714</a></dd>-->
<a
href="http://dev.w3.org/csswg/css3-lists/">http://dev.w3.org/csswg/css3-lists/</a>
@@ -735,8 +735,7 @@
<tr>
<th>Applies To:
- <td>all elements with ‘<code class=css>display:
- list-item</code>’
+ <td><a href="#list-item"><i title="list item">list items</i></a>
<tr>
<th>Inherited:
@@ -786,12 +785,12 @@
href="#list-style-image"><code
class=property>list-style-image</code></a>’ and ‘<a
href="#list-style-type"><code
- class=property>list-style-type</code></a>’; to resolve this
+ class=property>list-style-type</code></a>’. To resolve this
ambiguity, a value of ‘<a href="#none"><code
class=css>none</code></a>’ in the shorthand must be applied to
whichever of the two properties aren't otherwise set by the shorthand.
- <pre class=css-example>
+ <pre class="example css-example">
list-style: none disc;
/* Sets the image to ''none'' and the type to ''disc''. */
@@ -819,7 +818,7 @@
<p>Authors who use only the descendant selector may not achieve the results
they expect. Consider the following rules:
- <pre class=html-example>
+ <pre class="example html-example">
<!doctype html>
<html>
<head>
@@ -891,7 +890,7 @@
make the marker box positioned, which can have an effect on the computed
value of display.
- <div class=html-example>
+ <div class=example>
<p>In the following example, the content is centered within a marker box
of a fixed width. This document:</p>
@@ -936,7 +935,7 @@
<p>The next example uses markers to number notes (paragraphs).
- <div class=html-example>
+ <div class=example>
<p>The following document:</p>
<pre class=html-example>
@@ -978,7 +977,7 @@
</pre>
</div>
- <div class=html-example>
+ <div class=example>
<p>The following example illustrates how markers may be offset from their
element. This HTML application and style sheet:</p>
@@ -1031,15 +1030,13 @@
its ‘<code class=property>content</code>’ property set to
‘<code class=css>normal</code>’, the computed value of the
marker's ‘<code class=property>content</code>’ property must
- be constructed according to the following algorithm:
+ be determined according to the following algorithm:
<ol>
<li>If the computed value of ‘<a href="#list-style-image"><code
class=property>list-style-image</code></a>’ is a valid image, then
the computed value of the ‘<code
- class=property>content</code>’ property is the value of the
- ‘<a href="#list-style-image"><code
- class=property>list-style-image</code></a>’ property.
+ class=property>content</code>’ property is that image.
<li>Otherwise, if the computed value of ‘<a
href="#list-style-type"><code
@@ -1153,38 +1150,39 @@
<tr>
<th>Computed value:
- <td>same as CSS2.1
+ <td>see prose, otherwise same as CSS2.1
</table>
<p>The ‘<code class=css>marker</code>’ value for ‘<code
class=property>position</code>’ depends on the element it is set on
having a list item ancestor. If the specified value of ‘<code
class=property>position</code>’ is ‘<code
- class=css>marker</code>’ and the element does not have a list-item
+ class=css>marker</code>’ and the element does not have a list item
ancestor, ‘<code class=property>position</code>’ must compute
to ‘<code class=property>relative</code>’ on the element.
- <p>The box's vertical position is calculated according to the <a
+ <p>The element's vertical position is calculated according to the <a
href="http://www.w3.org/TR/CSS21/visuren.html#normal-flow">normal
flow</a>. <span class=note>In the Positioned Layout Module this will be
defined more precisely in terms of placeholders.</span>
- <p>To calculate the box's horizontal position, first define the box's
- nearest list item ancestor as the <dfn id=ancestor-list-item>ancestor list
- item</dfn>, and the parent of that box as the <dfn
- id=ancestor-list-container>ancestor list container</dfn>. The box's
- horizontal position must then be set such that the margin edge of the box
- corresponding to the "end" edge of the <a
- href="#ancestor-list-container"><i>ancestor list container</i></a> is
+ <p>To calculate the element's horizontal position, first define the
+ element's nearest list item ancestor element as the <dfn
+ id=ancestor-list-item>ancestor list item</dfn>, and the parent of
+ <em>that</em> element as the <dfn id=ancestor-list-container>ancestor list
+ container</dfn>. The element's horizontal position must then be set such
+ that the margin edge of the element corresponding to the "end" edge of the
+ <a href="#ancestor-list-container"><i>ancestor list container</i></a> is
flush with the border edge of the <a
href="#ancestor-list-item"><i>ancestor list item</i></a> corresponding to
the "start" edge of the <a href="#ancestor-list-container"><i>ancestor
- list container</i></a>. <span class=note>The purpose of this somewhat
- convoluted definition is to position the marker flush against its list
- item, and to keep all the markers for a given list on the same side of
- their list items even in mixed-direction text, so that authors can specify
- padding on only one side and still ensure their markers are
- visible.</span>
+ list container</i></a>.
+
+ <p class=note>The purpose of this somewhat convoluted definition is to
+ position the marker flush against its list item, and to keep all the
+ markers for a given list on the same side of their list items even in
+ mixed-direction text, so that authors can specify padding on only one side
+ and still ensure their markers are visible.
<p class=issue>This handles ltr/rtl mixed-direction text, but not mixed
horizontal and vertical text. For example, if the <a
@@ -1200,8 +1198,8 @@
class=property>right</code>’, ‘<code
class=property>bottom</code>’, and ‘<code
class=property>left</code>’ properties specify offsets relative to
- the top, right, bottom, and left edges (respectively) of the box itself,
- similar to how relative positioning works.</p>
+ the top, right, bottom, and left edges (respectively) of the element
+ itself, similar to how relative positioning works.</p>
<!-- ===================================================================== -->
<h2 id=counter-style><span class=secno>8. </span> Defining Custom Counter
@@ -1232,6 +1230,9 @@
<ul>
<li>a <dfn id=name title=counter-name>name</dfn>, to identify the style
+ <li>an <dfn id=algorithm title=counter-algorithm>algorithm</dfn> that
+ transforms counter values into a string representation
+
<li>a <dfn id=negative-sign title=counter-negative>negative sign</dfn>,
which is prepended or appended to the representation of a negative
counter value
@@ -1242,17 +1243,14 @@
<li>a <dfn id=suffix title=counter-suffix>suffix</dfn>, to append to the
representation
- <li>a <dfn id=fallback-style title=counter-fallback>fallback style</dfn>,
- to render the representation with when the counter value is outside the
- counter style's range or the counter style otherwise can't render the
- counter value
-
<li>an <dfn id=upper title=counter-upper-bound>upper</dfn> and <dfn
id=lower-range-bound title=counter-lower-bound>lower range bound</dfn>,
to specify the (inclusive) range that the counter style can handle
- <li>and an <dfn id=algorithm title=counter-algorithm>algorithm</dfn> that
- transforms counter values into a string representation
+ <li>and a <dfn id=fallback-style title=counter-fallback>fallback
+ style</dfn>, to render the representation with when the counter value is
+ outside the counter style's range or the counter style otherwise can't
+ render the counter value
</ul>
<p>The algorithm is usually specified implicitly by a combination of the
@@ -1292,6 +1290,15 @@
<li>Return the representation.
</ol>
+ <p class=note>Note that the prefix and suffix don't play a part in this
+ algorithm. This is intentional; the prefix and suffix aren't part of the
+ string returned by the counter() or counters() functions. Instead, the
+ prefix and suffix are added by the algorithm that constructs the computed
+ value of the ‘<code class=property>contents</code>’ property
+ for the ::marker pseudo-element. This also implies that the prefix and
+ suffix always come from the specified counter-style, even if the actual
+ representation is constructed by a fallback style.
+
<p>The general form of an ‘<code
class=css>@counter-style</code>’ rule is:
@@ -1301,30 +1308,29 @@
}
</pre>
- <p>Each @counter-style <dfn id=rule>rule</dfn> specifies a value for every
- counter-style descriptor, either implicitly or explicitly. Those not given
- explicit value in the rule take the initial value listed with each
- descriptor in this specification. These descriptors apply solely within
- the ontext of the @counter-style <dfn id=rule0>rule</dfn> in which they
- are defined, and do not apply to document language elements. There is no
- notion of which elements the descriptors apply to or whether the values
- are inherited by child elements. When a given descriptor occurs multiple
- times in a given @counter-style <dfn id=rule1>rule</dfn>, only the last
- specified value is used; all prior values for that descriptor are ignored.
+ <p>Each @counter-style rule specifies a value for every counter-style
+ descriptor, either implicitly or explicitly. Those not given explicit
+ value in the rule take the initial value listed with each descriptor in
+ this specification. These descriptors apply solely within the ontext of
+ the @counter-style rule in which they are defined, and do not apply to
+ document language elements. There is no notion of which elements the
+ descriptors apply to or whether the values are inherited by child
+ elements. When a given descriptor occurs multiple times in a given
+ @counter-style rule, only the last specified value is used; all prior
+ values for that descriptor are ignored.
- <p>User agents which do not understand the @counter-style <dfn
- id=rule2>rule</dfn> encounter the opening curly bracket and ignore forward
- until the closing curly bracket. This at-rule conforms with the
- forward-compatible parsing requirement of CSS; parsers may ignore these
- rules without error. Any descriptors that are not recognized or
- implemented by a given user agent must be ignored. @counter-style rules
- require a ‘<a href="#descdef-type"><code
- class=property>type</code></a>’ descriptor; if this is missing the
- @counter-style <dfn id=is>is</dfn> invalid and must be ignored. The
- <i><counter-style-name></i> must be be a valid identifier and must not
- be "decimal", "default", "inherit", "initial", "inside", "none", or
- "outside"; otherwise the @counter-style <dfn id=is0>is</dfn> invalid and
- must be ignored.
+ <p>User agents which do not understand the @counter-style rule encounter
+ the opening curly bracket and ignore forward until the closing curly
+ bracket. This at-rule conforms with the forward-compatible parsing
+ requirement of CSS; parsers may ignore these rules without error. Any
+ descriptors that are not recognized or implemented by a given user agent
+ must be ignored. @counter-style rules require a ‘<a
+ href="#descdef-type"><code class=property>type</code></a>’
+ descriptor; if this is missing the @counter-style is invalid and must be
+ ignored. The <i><counter-style-name></i> must be be a valid identifier
+ and must not be "decimal", "default", "inherit", "initial", "inside",
+ "none", or "outside"; otherwise the @counter-style is invalid and must be
+ ignored.
<h3 id=counter-style-type><span class=secno>8.1. </span> Counter
algorithms: the ‘<a href="#descdef-type"><code
@@ -1792,13 +1798,13 @@
<h4 id=override><span class=secno>8.1.7. </span> override</h4>
<p>The ‘<code class=css>override</code>’ type allows an author
- to use the representation-construction algorithm of another counter style,
- but alter other aspects, such as the negative sign or the suffix. If a
- counter style uses the ‘<code class=css>override</code>’ type,
- any unspecified descriptors are taken from the specified counter style,
- rather than taking their initial values.
+ to use the <i>algorithm</i> of another counter style, but alter other
+ aspects, such as the negative sign or the suffix. If a counter style uses
+ the ‘<code class=css>override</code>’ type, any unspecified
+ descriptors are taken from the specified counter style, rather than taking
+ their initial values.
- <p>If a @counter-style <dfn id=uses>uses</dfn> the ‘<code
+ <p>If a @counter-style uses the ‘<code
class=css>override</code>’ type, it must not contain a ‘<a
href="#descdef-glyphs"><code class=property>glyphs</code></a>’ or
‘<a href="#descdef-additive-glyphs"><code
@@ -2067,8 +2073,8 @@
href="#descdef-additive-glyphs"><code
class=property>additive-glyphs</code></a>’ descriptor must be
specified if the counter type is ‘<code
- class=css>additive</code>’; otherwise, the @counter-style <dfn
- id=is1>is</dfn> invalid and must be ignored.
+ class=css>additive</code>’; otherwise, the @counter-style is invalid
+ and must be ignored.
<p>Some counter styles specify that the ‘<a
href="#descdef-glyphs"><code class=property>glyphs</code></a>’
@@ -4122,7 +4128,7 @@
<p>All of the following styles are defined over the range 1-99. The glyphs
for each counter value must be the unicode glyph already defined for that
- value in the existing @counter-style <dfn id=rule3>rule</dfn>, or a
+ value in the existing @counter-style <dfn id=rule>rule</dfn>, or a
generated image in the same style with the counter value changed as
appropriate:
@@ -4354,7 +4360,7 @@
<td>see individual properties
- <td>all elements with ‘display: list-item’
+ <td>list items
<td>yes
@@ -4650,10 +4656,6 @@
<li>inside, <a href="#inside" title=inside><strong>4.</strong></a>
- <li>is, <a href="#is" title=is><strong>8.</strong></a>, <a href="#is0"
- title=is><strong>8.</strong></a>, <a href="#is1"
- title=is><strong>8.7.</strong></a>
-
<li>japanese-formal, <a href="#japanese-formal"
title=japanese-formal><strong>9.6.</strong></a>, <a
href="#japanese-formal0" title=japanese-formal><strong>11.1.</strong></a>
@@ -4824,11 +4826,7 @@
<li>range, <a href="#descdef-range" title=range><strong>8.5.</strong></a>
- <li>rule, <a href="#rule" title=rule><strong>8.</strong></a>, <a
- href="#rule0" title=rule><strong>8.</strong></a>, <a href="#rule1"
- title=rule><strong>8.</strong></a>, <a href="#rule2"
- title=rule><strong>8.</strong></a>, <a href="#rule3"
- title=rule><strong>11.2.</strong></a>
+ <li>rule, <a href="#rule" title=rule><strong>11.2.</strong></a>
<li>saho, <a href="#saho" title=saho><strong>9.3.</strong></a>
@@ -4935,8 +4933,6 @@
<li>upper-ukrainian-full, <a href="#upper-ukrainian-full"
title=upper-ukrainian-full><strong>9.3.</strong></a>
- <li>uses, <a href="#uses" title=uses><strong>8.1.7.</strong></a>
-
<li>wolaita, <a href="#wolaita" title=wolaita><strong>9.3.</strong></a>
<li>yemsa, <a href="#yemsa" title=yemsa><strong>9.3.</strong></a>
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-lists/Overview.src.html,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -d -r1.116 -r1.117
--- Overview.src.html 9 Jul 2011 01:23:00 -0000 1.116
+++ Overview.src.html 14 Jul 2011 01:35:36 -0000 1.117
@@ -390,7 +390,7 @@
<td>see individual properties
<tr>
<th>Applies To:
- <td>all elements with ''display: list-item''
+ <td><i title="list item">list items</i>
<tr>
<th>Inherited:
<td>yes
@@ -418,13 +418,9 @@
</pre>
</div>
- <p>Using a value of ''none'' in the shorthand
- is potentially ambiguous, as ''none'' is a valid value for both 'list-style-image'
- and 'list-style-type'; to resolve this ambiguity, a value of ''none'' in the
- shorthand must be applied to whichever of the two properties aren't otherwise
- set by the shorthand.</p>
+ <p>Using a value of ''none'' in the shorthand is potentially ambiguous, as ''none'' is a valid value for both 'list-style-image' and 'list-style-type'. To resolve this ambiguity, a value of ''none'' in the shorthand must be applied to whichever of the two properties aren't otherwise set by the shorthand.</p>
- <pre class='css-example'>
+ <pre class='example css-example'>
list-style: none disc;
/* Sets the image to ''none'' and the type to ''disc''. */
@@ -450,7 +446,7 @@
<p>Authors who use only the descendant selector may not
achieve the results they expect. Consider the following rules:</p>
- <pre class="html-example">
+ <pre class="example html-example">
<!doctype html>
<html>
<head>
@@ -506,11 +502,11 @@
<p>Just like other generated content, markers generate a box when they're created, which has margins, border, padding, and everything else a box normally has. Markers are placed at the beginning of their superior parent's content, before the ::before pseudo-element (if it exists). Marker boxes are inline by default, though certain values for 'list-style-position' on the list item can make the marker box positioned, which can have an effect on the computed value of display.</p>
- <div class="html-example">
+ <div class="example">
<p>In the following example, the content is centered within a marker
box of a fixed width. This document:</p>
- <pre class=html-example>
+ <pre class="html-example">
<!doctype html>
<html>
<head>
@@ -552,10 +548,10 @@
<p>The next example uses markers to number notes (paragraphs).</p>
- <div class="html-example">
+ <div class="example">
<p>The following document:</p>
- <pre class=html-example>
+ <pre class="html-example">
<!doctype html>
<html>
<head>
@@ -594,11 +590,11 @@
</pre>
</div>
- <div class="html-example">
+ <div class="example">
<p>The following example illustrates how markers may be offset from their element. This HTML
application and style sheet:</p>
- <pre class=html-example>
+ <pre class="html-example">
<!doctype html>
<html>
<head>
@@ -644,13 +640,12 @@
Generating the computed value of the 'content' property</h3>
<p>If a ''::marker'' pseudo-element has its 'content' property set to ''normal'',
- the computed value of the marker's 'content' property must be constructed
+ the computed value of the marker's 'content' property must be determined
according to the following algorithm:</p>
<ol>
<li>If the computed value of 'list-style-image' is a valid image, then
- the computed value of the 'content' property is the value of the
- 'list-style-image' property.</li>
+ the computed value of the 'content' property is that image.</li>
<li>Otherwise, if the computed value of 'list-style-type' is a string, then
the computed value of the 'content' property is that string.</li>
@@ -725,18 +720,17 @@
<td>same as CSS2.1
<tr>
<th>Computed value:
- <td>same as CSS2.1
+ <td>see prose, otherwise same as CSS2.1
</tbody>
</table>
- <p>The ''marker'' value for 'position' depends on the element it is set on having a list item ancestor. If the specified value of 'position' is ''marker'' and the element does not have a list-item ancestor, 'position' must compute to 'relative' on the element.</p>
+ <p>The ''marker'' value for 'position' depends on the element it is set on having a list item ancestor. If the specified value of 'position' is ''marker'' and the element does not have a list item ancestor, 'position' must compute to 'relative' on the element.</p>
- <p>The box's vertical position is calculated according to the
- <a href="http://www.w3.org/TR/CSS21/visuren.html#normal-flow">normal flow</a>.
- <span class='note'>In the Positioned Layout Module this will be defined
- more precisely in terms of placeholders.</span></p>
+ <p>The element's vertical position is calculated according to the <a href="http://www.w3.org/TR/CSS21/visuren.html#normal-flow">normal flow</a>. <span class='note'>In the Positioned Layout Module this will be defined more precisely in terms of placeholders.</span></p>
- <p>To calculate the box's horizontal position, first define the box's nearest list item ancestor as the <dfn>ancestor list item</dfn>, and the parent of that box as the <dfn>ancestor list container</dfn>. The box's horizontal position must then be set such that the margin edge of the box corresponding to the "end" edge of the <i>ancestor list container</i> is flush with the border edge of the <i>ancestor list item</i> corresponding to the "start" edge of the <i>ancestor list container</i>. <span class='note'>The purpose of this somewhat convoluted definition is to position the marker flush against its list item, and to keep all the markers for a given list on the same side of their list items even in mixed-direction text, so that authors can specify padding on only one side and still ensure their markers are visible.</span></p>
+ <p>To calculate the element's horizontal position, first define the element's nearest list item ancestor element as the <dfn>ancestor list item</dfn>, and the parent of <em>that</em> element as the <dfn>ancestor list container</dfn>. The element's horizontal position must then be set such that the margin edge of the element corresponding to the "end" edge of the <i>ancestor list container</i> is flush with the border edge of the <i>ancestor list item</i> corresponding to the "start" edge of the <i>ancestor list container</i>.</p>
+
+ <p class='note'>The purpose of this somewhat convoluted definition is to position the marker flush against its list item, and to keep all the markers for a given list on the same side of their list items even in mixed-direction text, so that authors can specify padding on only one side and still ensure their markers are visible.</p>
<p class='issue'>This handles ltr/rtl mixed-direction text, but not mixed
horizontal and vertical text. For example, if the <i>ancestor list container</i>
@@ -746,9 +740,7 @@
on what UI would be acceptable for such a crazy case, and how to state it
in non-crazy terms.</p>
- <p>The 'top', 'right', 'bottom', and 'left' properties specify offsets
- relative to the top, right, bottom, and left edges (respectively) of the box
- itself, similar to how relative positioning works.</p>
+ <p>The 'top', 'right', 'bottom', and 'left' properties specify offsets relative to the top, right, bottom, and left edges (respectively) of the element itself, similar to how relative positioning works.</p>
<!-- ===================================================================== -->
@@ -775,6 +767,9 @@
<ul>
<li>a <dfn title='counter-name'>name</dfn>, to identify the style</li>
+ <li>an <dfn title='counter-algorithm'>algorithm</dfn> that transforms counter
+ values into a string representation</li>
+
<li>a <dfn title='counter-negative'>negative sign</dfn>, which is prepended or
appended to the representation of a negative counter value</li>
@@ -782,16 +777,13 @@
<li>a <dfn title='counter-suffix'>suffix</dfn>, to append to the representation</li>
- <li>a <dfn title='counter-fallback'>fallback style</dfn>, to render the
- representation with when the counter value is outside the counter style's
- range or the counter style otherwise can't render the counter value</li>
-
<li>an <dfn title='counter-upper-bound'>upper</dfn> and
<dfn title='counter-lower-bound'>lower range bound</dfn>, to specify the
(inclusive) range that the counter style can handle</li>
- <li>and an <dfn title='counter-algorithm'>algorithm</dfn> that transforms counter
- values into a string representation</li>
+ <li>and a <dfn title='counter-fallback'>fallback style</dfn>, to render the
+ representation with when the counter value is outside the counter style's
+ range or the counter style otherwise can't render the counter value</li>
</ul>
<p>The algorithm is usually specified implicitly by a combination of the ''type'',
@@ -821,6 +813,8 @@
<li>Return the representation.</li>
</ol>
+ <p class='note'>Note that the prefix and suffix don't play a part in this algorithm. This is intentional; the prefix and suffix aren't part of the string returned by the counter() or counters() functions. Instead, the prefix and suffix are added by the algorithm that constructs the computed value of the 'contents' property for the ::marker pseudo-element. This also implies that the prefix and suffix always come from the specified counter-style, even if the actual representation is constructed by a fallback style.</p>
+
<p>The general form of an ''@counter-style'' rule is:</p>
<pre>
@@ -829,25 +823,25 @@
}
</pre>
- <p>Each @counter-style <dfn>rule</dfn> specifies a value for every counter-style descriptor,
+ <p>Each @counter-style rule specifies a value for every counter-style descriptor,
either implicitly or explicitly. Those not given explicit value in the rule
take the initial value listed with each descriptor in this specification.
- These descriptors apply solely within the ontext of the @counter-style <dfn>rule</dfn>
+ These descriptors apply solely within the ontext of the @counter-style rule
in which they are defined, and do not apply to document language elements.
There is no notion of which elements the descriptors apply to or whether the
values are inherited by child elements. When a given descriptor occurs
- multiple times in a given @counter-style <dfn>rule</dfn>, only the last specified value
+ multiple times in a given @counter-style rule, only the last specified value
is used; all prior values for that descriptor are ignored.</p>
- <p>User agents which do not understand the @counter-style <dfn>rule</dfn> encounter the
+ <p>User agents which do not understand the @counter-style rule encounter the
opening curly bracket and ignore forward until the closing curly bracket.
This at-rule conforms with the forward-compatible parsing requirement of CSS;
parsers may ignore these rules without error. Any descriptors that are not
recognized or implemented by a given user agent must be ignored. @counter-style
- rules require a 'type' descriptor; if this is missing the @counter-style <dfn>is</dfn>
+ rules require a 'type' descriptor; if this is missing the @counter-style is
invalid and must be ignored. The <i><counter-style-name></i> must be be
a valid identifier and must not be "decimal", "default", "inherit", "initial",
- "inside", "none", or "outside"; otherwise the @counter-style <dfn>is</dfn> invalid and
+ "inside", "none", or "outside"; otherwise the @counter-style is invalid and
must be ignored.</p>
<h3 id='counter-style-type'>
@@ -1269,13 +1263,9 @@
<h4>
override</h4>
- <p>The ''override'' type allows an author to use the representation-construction
- algorithm of another counter style, but alter other aspects, such as the
- negative sign or the suffix. If a counter style uses the ''override'' type,
- any unspecified descriptors are taken from the specified counter style, rather
- than taking their initial values.</p>
+ <p>The ''override'' type allows an author to use the <i>algorithm</i> of another counter style, but alter other aspects, such as the negative sign or the suffix. If a counter style uses the ''override'' type, any unspecified descriptors are taken from the specified counter style, rather than taking their initial values.</p>
- <p>If a @counter-style <dfn>uses</dfn> the ''override'' type, it must not contain a
+ <p>If a @counter-style uses the ''override'' type, it must not contain a
'glyphs' or 'additive-glyphs' descriptor; otherwise it is invalid and must
be ignored. If the specified counter style name isn't the name of any
currently-defined counter style, it must be treated as if it was overriding
@@ -1468,7 +1458,7 @@
The 'glyphs' descriptor must be specified if the counter type is ''repeating'',
''numeric'', ''alphabetic'', ''symbolic'', or ''non-repeating'', and the
'additive-glyphs' descriptor must be specified if the counter type is
- ''additive''; otherwise, the @counter-style <dfn>is</dfn> invalid and must be ignored.</p>
+ ''additive''; otherwise, the @counter-style is invalid and must be ignored.</p>
<p>Some counter styles specify that the 'glyphs' descriptor must have at
least two entries. If the counter's style is such a type, and the 'glyphs'
Received on Thursday, 14 July 2011 01:35:41 UTC