Re: [csswg-drafts] [css-lists-3] counter-set vs counter-increment (#3810)

The CSS Working Group just discussed `apply counter-set after counter-increment`, and agreed to the following:

* `RESOLVED: apply counter-set after counter-increment`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic:apply counter-set after counter-increment<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3810<br>
&lt;dael> fantasai: This was an issue around interaction. Property values you have to set if you're incremeneting on every item and want to set to a particular value. yOu have to set it minus increment. That's ergonomically awk<br>
&lt;fremy> (I'm in favor)<br>
&lt;dael> fantasai: Suggestion is set counter set after increment so if you set foo 5 it will be 5 no matter the counter increment<br>
&lt;dael> fantasai: Generally better cascading behavior. Counterset wins over counter incrememnt rather than adding to it.<br>
&lt;dael> gregwhitworth: When you set counterset it starts from that place?<br>
&lt;dael> fantasai: Sets an explicit value for the counter<br>
&lt;dael> gregwhitworth: And doesn't inc after that?<br>
&lt;dael> fantasai: If you have nth-child 5 counterset: chapter 5 it will have 5 instead of the increment added to that.<br>
&lt;dael> gregwhitworth: Then increment from 5?<br>
&lt;dael> fantasai: On other elements, yeah.<br>
&lt;dael> fantasai: On a particular element you apply counter-reset then counter increment then counter set<br>
&lt;dael> plinss: Makes sense to me. Looking at issue Gecko impl but will change. Any other impl here?<br>
&lt;dael> fantasai: I think they're only ones. They committed the fix a day ago<br>
&lt;dael> plinss: Objections?<br>
&lt;dael> RESOLVED: apply counter-set after counter-increment<br>
</details>


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

Received on Wednesday, 10 April 2019 16:09:38 UTC