- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 06 Apr 2019 00:08:33 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-lists-3] counter-set vs counter-increment == There's some ergonomc awkwardness about `counter-set` vs `counter-increment`, e.g. in https://github.com/w3c/csswg-drafts/issues/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.) 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). Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3810 using your GitHub account
Received on Saturday, 6 April 2019 00:08:35 UTC