- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Apr 2021 15:23:08 +0000
- To: public-css-archive@w3.org
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-lists] `counter-reset` should be able to compute to `reversed()` without integer == See https://drafts.csswg.org/css-lists/#propdef-counter-reset > Computed value: the keyword `none` or a list, each item an identifier or a `reversed()` function paired with an integer I think this should be > Computed value: the keyword `none` or a list, each item an identifier or a `reversed()` function **optionally** paired with an integer Because if you use `counter-reset: inherit` and the parent had `counter-reset: reversed(c)`, I guess you want to recalculate the start value in the subscope, instead of inheriting the start value of the parent. Thus the start value shouldn't be part of the computed value. As https://drafts.csswg.org/css-lists/#instantiating-counters says, > When a counter is instantiated without an initial value, the user agent must dynamically calculate the initial value **at layout-time** to be the number of elements and pseudo-elements that instantiate the same counter in the same scope, plus 1. So not at computed-value time but at layout-time. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6232 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 April 2021 15:23:14 UTC