W3C home > Mailing lists > Public > www-style@w3.org > January 2010

Counter-reset on pseudo class creates new counter-scope

From: divya manian <divya.manian@gmail.com>
Date: Mon, 4 Jan 2010 09:20:50 -0800
Message-ID: <40fb5ba21001040920s4f522565k7a783bf9585f9def@mail.gmail.com>
To: www-style@w3.org
Hi all

I was trying nested counters when I came across this strange behavior.

Demo: http://nimbupani.com/demo/nested-counter.html

The behavior is, when I use this in CSS:

		ol {
	  ol li {
			counter-increment: section;

		ol li:nth-child(4n)		
		ol li:before {                      			
			content: counter(section)" ";
		ol li li:before {                      			
			content: counters(section, " ")" ";

The nested element seems to create another counter named section which
has scope for only nth-child pseudo-class (even though they are only
resetting the counter named section). While this seems consistent with
the Candidate Recommendation [2], each browser seems to interpret this
differently. Chrome/Safari/Opera (latest versions) resets that counter
to 1. Firefox resets that to the last number before the counter is

The counter-reset set on classes/pseudo-classes is creating a new
scope even though they are overriding the counter-increment specified
on the same element. I think this behavior is incorrect (even though
valid according to the spec).


[2] http://www.w3.org/TR/CSS2/generate.html
Received on Monday, 4 January 2010 17:21:23 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:31 UTC