Re: [csswg-drafts] [css-lists] Should list-item counter reset rule be in a UA stylesheet? (#4244)

The CSS Working Group just discussed `Should list-item counter reset rule be in a UA stylesheet?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: Should list-item counter reset rule be in a UA stylesheet?<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/4244<br>
&lt;heycam> emilio: the CSS Lists spec says that ol and ul (should also include menu!) should have a counter-reset: list-item in the UA sheet<br>
&lt;heycam> .. we've had 2 regression reports, people overriding counter-reset<br>
&lt;heycam> ... the fix on the author side is trivial, adding list-item to the value<br>
&lt;heycam> ... afaik, the 2 regressions are fixed that way<br>
&lt;heycam> ... but we may want to think about whether we should make this reset magical<br>
&lt;heycam> ... the issue with making it magical, is that there's no way to override it to none<br>
&lt;heycam> TabAtkins: at the previous meeting, didn't we resolve to do the thing where if you don't mention list-item?<br>
&lt;heycam> emilio: that's for counter-increment<br>
&lt;heycam> ... should we do the same for counter-reset?<br>
&lt;heycam> ... the reason I didn't want to jump to do that, there's no way to override it to none<br>
&lt;heycam> ... could say you add the counter-reset, unless you explicitly set it to none<br>
&lt;heycam> ... so it's tricky<br>
&lt;heycam> ... not totally convinced we need to change it for compat, but I'd like to know if we do need it<br>
&lt;heycam> TabAtkins: if we wanted to express the reverse mbehavior, in non magical ways, you'd need something special for counter-reset<br>
&lt;heycam> ... the only way to do that within the syntax of counter-reset would be to add a function<br>
&lt;heycam> ... because there's no comma, must be an ident and possibly a number.   if you add a number ident, that's just another counter<br>
&lt;heycam> ... if you wanted to change hte behavior, like with reversed lists, synatx would be to use a function rather than an ident<br>
&lt;heycam> ... could have a dont-reset(...) when you explicitly need to<br>
&lt;heycam> ... then if it's not explicitly mentioned in this way, it gets reset in this way<br>
&lt;heycam> emilio: not a fan<br>
&lt;heycam> AmeliaBR: counter-reset: dont-reset(list-item), xxx<br>
&lt;heycam> emilio: just looking for ideas if we needed to tackle this<br>
&lt;heycam> ... for now this is fine I think<br>
&lt;heycam> ... a more web compatible solution would be to always reset it, but then it's annoying you can't override it<br>
&lt;heycam> TabAtkins: you can override the use of it<br>
&lt;heycam> emilio: the browser's doing some extra accounting in the background, but the author just wouldn't use it<br>
&lt;heycam> s/emilio/TabAtkins/<br>
&lt;heycam> fremy: what happens if you don't reset, and you have a reversed list inside another reversed list?<br>
&lt;heycam> AmeliaBR: it's a nested counter<br>
&lt;heycam> fremy: if you're not resetting th ecounter, you have to consider the nested child as part of the main list<br>
&lt;heycam> ... does anyone want to implement that?<br>
&lt;heycam> emilio: I think it would work right now<br>
&lt;heycam> AmeliaBR: the list items handle if you're incrementing up or down<br>
&lt;heycam> emilio: we do the counting on the counter nodes, so we count the number of counter nodes that are in the same list<br>
&lt;heycam> ... I think it would work.  mixing reversed and non-reversed lists would be fun...<br>
&lt;heycam> fremy: not sure it's a big problem if we cannot<br>
&lt;heycam> AmeliaBR: any interested in supporting reversed counters in general?  counter-reset and reset it to the max value the counter would have?<br>
&lt;heycam> TabAtkins: so far no, since that's what reversed counters actually do in HTML<br>
&lt;TabAtkins> s/that's not/that's not what/<br>
&lt;TabAtkins> s/that's what/that's not what/<br>
&lt;TabAtkins> ScribeNick: TabAtkins<br>
</details>


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

Received on Monday, 16 September 2019 07:49:17 UTC