W3C home > Mailing lists > Public > www-style@w3.org > March 2009

Re: Counter-increment is not clear in CSS21 and CSS3 (was: Re: Bug in IE8?)

From: L. David Baron <dbaron@dbaron.org>
Date: Tue, 17 Mar 2009 19:45:10 -0500
To: www-style@w3.org
Message-ID: <20090318004510.GA22669@pickering.dbaron.org>
On Thursday 2009-03-12 22:21 +0100, Fran├žois REMY wrote:
> But, I just found another problem : The spec isn't clear about how the UA must 
> treat 'none' as value for counter-increment. In fact, the prose NEVER talk about 
> the effect of 'none'. So, the browser should treat none as a non-effect value, if it 
> can't understand it otherly.

I agree that the spec should be clarified here.

I think IE8's behavior (not accepting 'none') is incorrect.  But I
also think Gecko's behavior (it rejects 'none 1' but accepts 'foo 1
none 1') is incorrect.

I think we probably want to say that either:

 (1) 'none' is a valid value on its own, but any value containing
 'none' as a counter name is invalid, or

 (2) 'none' as a value on its own means that no counters are
 incremented/reset, but use of 'none' in any other values implies
 that there is a valid counter named 'none'.

Note that the same issue is present with 'inherit' and (in css3)
'initial'.

-David

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/
Received on Wednesday, 18 March 2009 00:45:46 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:17 GMT