- From: Tab Atkins Jr.. via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 06 Dec 2011 18:48:35 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-lists
In directory hutz:/tmp/cvs-serv1808
Modified Files:
Overview.html Overview.src.html
Log Message:
Make the cascading behavior of @counter-style slightly clearer.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-lists/Overview.html,v
retrieving revision 1.123
retrieving revision 1.124
diff -u -d -r1.123 -r1.124
--- Overview.html 6 Dec 2011 18:41:16 -0000 1.123
+++ Overview.html 6 Dec 2011 18:48:32 -0000 1.124
@@ -1479,6 +1479,10 @@
declaration "wins": first, they are compared by origin, with author rules
beating user rules, and user rules beating UA rules; second, they are
compared by document order, with later rules beating earlier rules.
+ ‘<code class=css>@counter-style</code>’ rules cascade
+ "atomically" - if one replaces another of the same name, it replaces it
+ <em>entirely</em>, rather than just replacing the specific descriptors it
+ specifies.
<p>This at-rule conforms with the forward-compatible parsing requirement of
CSS; parsers may ignore these rules without error. Any descriptors that
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-lists/Overview.src.html,v
retrieving revision 1.170
retrieving revision 1.171
diff -u -d -r1.170 -r1.171
--- Overview.src.html 6 Dec 2011 18:41:16 -0000 1.170
+++ Overview.src.html 6 Dec 2011 18:48:32 -0000 1.171
@@ -895,7 +895,7 @@
multiple times in a given @counter-style rule, only the last specified value
is used; all prior values for that descriptor must be ignored.</p>
- <p>Defining a ''@counter-style'' must make it available to the entire document in which it is included. If multiple ''@counter-style'' rules are defined with the same name, standard cascade rules must be used to determine which declaration "wins": first, they are compared by origin, with author rules beating user rules, and user rules beating UA rules; second, they are compared by document order, with later rules beating earlier rules.</p>
+ <p>Defining a ''@counter-style'' must make it available to the entire document in which it is included. If multiple ''@counter-style'' rules are defined with the same name, standard cascade rules must be used to determine which declaration "wins": first, they are compared by origin, with author rules beating user rules, and user rules beating UA rules; second, they are compared by document order, with later rules beating earlier rules. ''@counter-style'' rules cascade "atomically" - if one replaces another of the same name, it replaces it <em>entirely</em>, rather than just replacing the specific descriptors it specifies.</p>
<p>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. 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.</p>
Received on Tuesday, 6 December 2011 18:48:38 UTC