W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

Re: [csswg-drafts] [css-lists] Is the list-item counter increment for list items reflected in the computed style? (#3769)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 10 Apr 2019 16:32:39 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-481765126-1554913958-sysbot+gh@w3.org>
The CSS Working Group just discussed `Is the list-item counter increment for list items reflected in the computed style?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Is the list-item counter increment for list items reflected in the computed style?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3769<br>
&lt;dael> emilio: There's a magic increment applied to list items that's defined in terms of display. Element with display styling you have the magic counter increment depending on if list is incremented [missed]<br>
&lt;dael> emilio: Another possible thing to do is to just do it at used value time<br>
&lt;dael> emilio: I don't feel too strongly either way, maybe other engines have constraints on when can shuffle elements. As an author don't know if it's very useful to gCS with this counter. If you spec counter-incremeent:none and computed style is not none<br>
&lt;dael> fremy: I think it's not included in counter style<br>
&lt;fremy> ^ (in Edge)<br>
&lt;fremy> ^ (which is good because it probably should not inherit)<br>
&lt;dael> AmeliaBR: Clarification. When author says counter-increment:none it doesn't cancelt he list item incremement. Based on rule serialization should be as short as poss if omitting list item 1 have same effect as spec shouldn't shortest version be to omit it?<br>
&lt;emilio> Ugh, audio went nuts<br>
&lt;dael> plinss: Looks like emilio is having audio issues. Still there emilio ?<br>
&lt;dael> [silence]<br>
&lt;emilio> on irc yes<br>
&lt;dael> plinss: He's IRC only at this point<br>
&lt;dael> plinss: Any other thoughts on this?<br>
&lt;emilio> We could also do what AmeliaBR mentions, but that is only ommittable depending on the display value, so it's a bit weird to serialize differently depending on other property values<br>
&lt;emilio> fremy's point about inheritance is a good point<br>
&lt;dael> plinss: Should we defer until emilio can be on a call? He's responding on IRC<br>
&lt;dael> gregwhitworth: Let's defer if he's not able to get one<br>
&lt;dael> s/one/on<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3769#issuecomment-481765126 using your GitHub account
Received on Wednesday, 10 April 2019 16:32:43 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:46 UTC