- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Jun 2023 04:22:11 +0000
- To: public-css-archive@w3.org
A few additional points I'd like to make: 1. The ready-made counter styles definitions aren't going away. Authors can still create their own counter styles which both A) can be tweaked at a finer-grained way than swapping out the whole counter style for another, and B) are forward-compatible and won't change with future browser updates. 2. I think much of the arguments [above](https://github.com/w3c/csswg-drafts/issues/8636#issuecomment-1594317071) are making the perfect the enemy of the good. Are there people who want to specify in great detail the counter style algorithm to use on their webpages? Sure. Are there other people would just want the browser defaults for their language? Certainly. 3. This kind of "simple things simple, complex things possible" is central to the design of CSS. An analogy: it's possible for an author to implement letter-spacing themselves by wrapping every letter in their content in a `<span>` - and people can do that if they want super fine control over how letter spacing is applied. But we still offer the `letter-spacing` property for the people who just want the default behavior which is sufficient for most people. 4. If there are, in fact, corrections to be made to these ready-made counter styles, it's way easier to update ~3 major browsers than it is to update all the websites which use them. I also expect browsers would stay up-to-date with the spec, as updating these rules is essentially a data change, which is cheap from a browser developer's point of view. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8636#issuecomment-1600051783 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 June 2023 04:22:13 UTC