- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jul 2023 17:01:35 +0000
- To: public-css-archive@w3.org
Hm, actually I think ignoring the increment makes more sense than clamping. If you're, say, incrementing by 1000 for some visual reason, having a counter suddenly end in `647` or something, rather than `000` like all the others did, would look pretty weird. This does make the behavior slightly inconsistent with set/reset, which will indeed give you the unexpected value, but it's (slightly) more likely that increment will run into this case (due to a very large list) than set/reset (requiring you to purposely set a very large number). Plus there's no real way to infer intent from set/reset, so we can't change the value to something else close to the maximum range, while increment does have at least a little intent we can infer. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9029#issuecomment-1622153554 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 5 July 2023 17:01:37 UTC