Re: [csswg-drafts] [css-lists-3] counter-increment and counter-reset overflow/underflow (#9029)

The CSS Working Group just discussed `[css-lists-3] counter-increment and counter-reset overflow/underflow`, and agreed to the following:

* `RESOLVED: counter-increment is ignored on overflow`
* `RESOLVED: counter-increment will ignore the increment if it underflows or overflows`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> vitorroriz: currently spec says that if counter-increment overflow should clamp<br>
&lt;myles> q+ to clarify "overflow<br>
&lt;emilio> ... FF and chrome ignore the increment instead<br>
&lt;emilio> ... WebKit behavior is arguably a bug, so I was looking at how to fix this<br>
&lt;emilio> myles: just clarifying that overflow is not about layout overflow, just integer overflow, right?<br>
&lt;Rossen_> q?<br>
&lt;Rossen_> ack myles<br>
&lt;Zakim> myles, you wanted to clarify "overflow<br>
&lt;emilio> [multiple]: Yes<br>
&lt;myles> s/, right?//<br>
&lt;emilio> TabAtkins: I think I like the ignore behavior more than clamping for incrementing<br>
&lt;emilio> ... if you do counter-increment: 1billion, and you'd eventually get to INT32_MAX<br>
&lt;emilio> ... seems better to stick to &lt;last-valid-increment><br>
&lt;emilio> ... for set/reset I think clamping makes more sense<br>
&lt;fantasai> s/INT32_MAX/INT32_MAX, which looks weird/<br>
&lt;emilio> ... I don't have a strong opinion on this<br>
&lt;emilio> fantasai: I support all of Tab's arguments, and that's what we should do<br>
&lt;Rossen_> ack fantasai<br>
&lt;emilio> ... doesn't seem like an implementation problem<br>
&lt;emilio> TabAtkins: proposed resolution is "do the Gecko and Blink behavior"<br>
&lt;emilio> ... so change the spec so that increment ignores rather than clamps<br>
&lt;emilio> RESOLVED: counter-increment is ignored on overflow<br>
&lt;emilio> RESOLVED: counter-increment will ignore the increment if it underflows or overflows<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9029#issuecomment-1642508074 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 July 2023 17:51:44 UTC