- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Oct 2021 13:31:37 +0000
- To: public-css-archive@w3.org
> No magic flags that can only be set by HTML please. Yes, it would need magic to set the reversed flag. But now we already have some magic in order to produce either `counter-increment: list-item 1` or `counter-increment: list-item -1`. > Your second suggestion is interesting, but I doubt it's web-compatible. I think it's probably web compatible. Chromium completely ignored `counter-increment` and `counter-set` for `list-item` counter (except in `content: counter(list-item)`) until 89.0.4353.0 https://crrev.com/835809. And this was changed just to implement `<summary>` as a list item with `counter-increment: list-item 0`, not because authors were complaining the functionality was broken. So I doubt there's a lot of existing content relying on `counter-increment: list-item X`. > E.g. `counter-increment: c step(2)` which could mean 2 or -2 depending on the context Not a bad idea. But then maybe `<reversed-counter-name> <integer>` should wait until we have something like that. Otherwise it seems confusing to be able to declare reversed lists that completely behave like non-reversed ones. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6231#issuecomment-945771270 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 October 2021 13:31:39 UTC