- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Dec 2023 00:54:09 +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: Revert the previous resolution and the associated edits` * `RESOLVED: The working group is interested in defining an opt-in narrow scope for counter resets. Exact syntax tbd` <details><summary>The full IRC log of that discussion</summary> <dael> TabAtkins: A little while ago...several years...we talked about what changes to make to the counter scoping algo to make it workable as a mech to explain html lists<br> <dael> TabAtkins: html lists have weird behaviors for legacy reasons. I tried to write a fix that fixed what's in the thread but there's close behavior it did not solve. A related change that would fix both is define a counter has an associated scope, wide or narro. Default is wide where it's visible to children and following siblings until scope of same name is declared. Narrow is only visible to children<br> <dael> TabAtkins: That matched how counters. You have an ol and outside of that you have an li, today b/c wide scoping the li sees the counter scope from the ol and will increment that.<br> <dael> TabAtkins: There's some reasonable cases that are less intuitive due to wide.<br> <dael> TabAtkins: Ability to declare scope to be narrow fixes this properly. It will be somewhat magic same way list item counter is. Will be slightly more reasonable for authors where they intent it to number a list among children<br> <dael> TabAtkins: Concept also carried to when thinking about toggles. Having wide and narrow was necessary there. I think it's proved out that is useful.<br> <dael> TabAtkins: Precise mechanics I have not figured out. happy to take a resolution to figure out<br> <dael> florian: Wide is default and narrow is opt-in to match html?<br> <dael> TabAtkins: Correct<br> <dael> astearns: Other questions or opinions?<br> <dael> astearns: First thing would be revert previous?<br> <dael> astearns: Prop: Revert the previous resolution and the associated edits<br> <dael> astearns: Obj?<br> <dael> RESOLVED: Revert the previous resolution and the associated edits<br> <TabAtkins> valid markup that gets weird currently is in https://github.com/w3c/csswg-drafts/issues/9076<br> <dael> astearns: Prop: The working group is interested in defining an opt-in narrow scope for counter resets. Exact syntax tbd<br> <dael> TabAtkins: I expect it'll work same as reverse counter specs, but I haven't dug in enough to be certain<br> <dael> astearns: Obj?<br> <dael> florian: Question- you mentioned html has weird edge case. narrow scope seems too clean to cover. Do we end up matching html or is there a bajillion corner cases where we're different?<br> <dael> TabAtkins: I think this brings us all the way or very very close enough that browsers could call it good. I know wide behavior is web breaking if applied to html counters<br> <dael> florian: We'll discover it soon enough. We create narrow and if it doesn't work people will tell us<br> <dael> TabAtkins: I think remaining weird was list item counter and we resolved how to handle that. Where if you don't declare on an ol it happens. I'm not completely loaded on this and it's complex<br> <dael> RESOLVED: The working group is interested in defining an opt-in narrow scope for counter resets. Exact syntax tbd<br> <dael> TabAtkins: 9076 was also this as well. It was the same case<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-1843956580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 December 2023 00:54:11 UTC