- From: Vitor Roriz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Jul 2023 18:31:00 +0000
- To: public-css-archive@w3.org
vitorroriz has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-lists-3] counter-increment and counter-reset overflow/underflow == [Specification says](https://drafts.csswg.org/css-lists-3/#auto-numbering): > UAs may have implementation-specific limits on the maximum or minimum value of a counter. If a counter reset, set, or increment would push the value outside of that range, the value must be clamped to that range. However, gecko and blink behavior is: `counter-reset(<overflow/underflow-int-32-number>)` : clamp to range `counter-increment()` : ignore operation, keep current value WebKit behavior is: `counter-reset(<overflow/underflow-int-32-number>)` : clamp to range `counter-increment()` : overflow/underflow I'd like to discuss whether the expected behavior is "clamp to range", or if we should ignore operation for the `counter-increment()` case, since 2 vendors already do that and update the spec. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9029 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 4 July 2023 18:31:02 UTC