Re: Counter properties in CSS Lists Editor's Draft
There's some ergonomc awkwardness about counter-set vs counter-increment, e.g. in #3686 it's pointed out that you'd have to zero out the list-item increment when setting the counter for <li value=...>. (This particular case is technically problematic as well as unweildy because it'd get wiped out by an author counter-increment declaration; but there's some awkwardness either way and it doesn't cascade well for anyone.)
I'm wondering if instead of applying counter-reset, then counter-set, then counter-increment, we should apply counter-reset, then counter-increment, then counter-set? Then when you “set” a counter on an element, you actually get that value back, which seems a little more intuitive (and also solves the list-item problem).
Re: Counter properties in CSS Lists Editor's Draft
There's some ergonomc awkwardness about
counter-setvscounter-increment, e.g. in #3686 it's pointed out that you'd have to zero out the list-item increment when setting the counter for<li value=...>. (This particular case is technically problematic as well as unweildy because it'd get wiped out by an authorcounter-incrementdeclaration; but there's some awkwardness either way and it doesn't cascade well for anyone.)I'm wondering if instead of applying
counter-reset, thencounter-set, thencounter-increment, we should applycounter-reset, thencounter-increment, thencounter-set? Then when you “set” a counter on an element, you actually get that value back, which seems a little more intuitive (and also solves the list-item problem).