- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Oct 2020 16:29:30 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-lists] CSS counter scope/inheritance is incompatible with HTML ordinals`, and agreed to the following: * `RESOLVED: change CSS Lists to make all CSS counters behave differently for this case` <details><summary>The full IRC log of that discussion</summary> <emilio> Topic: [css-lists] CSS counter scope/inheritance is incompatible with HTML ordinals<br> <emilio> github: https://github.com/w3c/csswg-drafts/issues/5477<br> <emilio> TabAtkins: when I was writing the counter rules I was working from css 2.1 and my testing<br> <emilio> ... I knew HTML <ol> didn't match CSS counters in invalid markup<br> <emilio> ... Gecko tried to switch to counters for CSS lists<br> <emilio> ... and found out that they were not web compatible<br> <emilio> ... see the example in the issue with a nested <ol> directly under another<br> <emilio> ... html renders that as you'd probably expect<br> <emilio> ... that's also what editors generate for some reason<br> <emilio> ... In order to fix it we can specify that either html is magic<br> <emilio> ... that the list-item counter is magic<br> <emilio> ... or switch counter behavior<br> <emilio> ... mats is going for the later<br> <Rossen_> q<br> <emilio> ... and is proposing to do an ancestor-only check and only if that fails we look for a previous sibling counter<br> <emilio> ... that's probably fine and would still work with the main sibling use case which is naming headers<br> <emilio> ... so I'm ok with making that change<br> <emilio> Rossen_: you're referring to the third approach in the comment?<br> <emilio> TabAtkins: no, number 1<br> <dbaron> seems like a reasonable way to fix this without breaking use of counter numbering for headers<br> <emilio> fantasai: if you look at the example and replace list with section and item with h1, it will end up giving a better result<br> <emilio> ... I'm in favor of this change<br> <Rossen_> ack fantasai<br> <emilio> ... if we can pull it of<br> <emilio> off<br> <emilio> q+<br> <astearns> and you’re OK with this, faceless2?<br> <fantasai> emilio: We actually have made this change, unsure if released yet<br> <fantasai> emilio: but haven't heard of any breakage<br> <fantasai> Rossen_: cool<br> <faceless2> yes. everything I had to say on the topic before was wrong :-)<br> <emilio> Rossen_: objections?<br> <fantasai> strong +1 given emilio's report :)<br> <emilio> RESOLVED: change CSS Lists to make all CSS counters behave differently for this case<br> <emilio> [... discussion about republishing CSS2 ...]<br> <oriol> The change is in Firefox 82, which seems it was released on 2020-10-20 (but I still don't have it)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5477#issuecomment-714611576 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 October 2020 16:29:32 UTC