- From: L. David Baron <dbaron@dbaron.org>
- Date: Wed, 26 Mar 2014 12:56:57 -0700
- To: www-style@w3.org
- Message-ID: <20140326195657.GA9757@crum.dbaron.org>
http://dev.w3.org/csswg/css-counter-styles/#counter-style-fallback says: # Value: <counter-style-name> http://dev.w3.org/csswg/css-counter-styles/#counter-style-speak-as says: # Value: auto | numeric | alphabetic | bullet | <counter-style-name> both link to http://dev.w3.org/csswg/css-counter-styles/#typedef-counter-style-name which says: # The <counter-style-name> must be be a valid identifier and must # not be decimal or none, or else the rule is invalid. It seems like it's probably unintentional to disallow 'decimal' and 'none' from the values of 'fallback' and 'speak-as' -- especially decimal, anyway. If that was the intent (and I'm going to assume it was for purposes of reviewing the patches to implement this in Gecko, which matches what the patches currently do), I think it would help to separate the definition of <counter-style-name> from the definition of the @counter-style rule, and then have the prose forbidding 'decimal' and 'none' specifically in the section on the @counter-style rule and not as part of the definition of <counter-style-name>. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
Received on Wednesday, 26 March 2014 19:57:23 UTC