- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 09:10:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Reconsider <An+B># for :heading`, and agreed to the following: * `RESOLVED: change spec to list of integers` <details><summary>The full IRC log of that discussion</summary> <ydaniv> TabAtkins: some context, what whatwg was doing regarding heading level<br> <ydaniv> ... this issue is about design of functional form of heading()<br> <ydaniv> ... per spec it takes a comma separated list of An+B<br> <ydaniv> ... Ana wanted to simplify this<br> <fantasai> s/Ana/Anne<br> <ydaniv> ... wanted An+B<br> <ydaniv> ... I pushed back and suggested to do comma separated integers<br> <ydaniv> ... some discussion back and forth<br> <ydaniv> ... Anne is pushing back on pseudo classes for some reason<br> <kbabbitt> q+<br> <ydaniv> ... my suggestion is to do comma separated integers<br> <fantasai> s/pseudo classes/comma-separated lists/<br> <astearns> ack lea<br> <astearns> ack kbabbitt<br> <ydaniv> kbabbitt: wanted more details on the discussion<br> <ydaniv> ... it allows now 6 levels in HTML<br> <ydaniv> ... is this allowing more levels? or disassocating from HTML?<br> <ydaniv> TabAtkins: both<br> <SebastianZ> q+<br> <ydaniv> ... use generic tag and have it not rely on tag name<br> <ydaniv> ... but also to allow more levels, arbitrary number of levels<br> <TabAtkins> s/arbitrary/not arbitrary/<br> <astearns> ack SebastianZ<br> <ydaniv> SebastianZ: should it be restricted to just 9? or more?<br> <ydaniv> TabAtkins: the pseudo class should allow you any number<br> <astearns> ack fantasai<br> <Zakim> fantasai, you wanted to respond<br> <ydaniv> fantasai: we can allow any number<br> <florian> q+<br> <ydaniv> ... we aren't going to limit it<br> <astearns> ack florian<br> <ydaniv> ... syntax is optimized for it<br> <noamr> q+<br> <ydaniv> florian: I have a hard time for allowing these patterns<br> <SebastianZ> q+<br> <ydaniv> ... would rather have comma separated to be simpler<br> <astearns> ack noamr<br> <ydaniv> noamr: there is presedence for comma separated<br> <fantasai> s/presedence/precedence/<br> <ydaniv> ... when you have list items, you don't know how many are going to be, and relationship is linear<br> <oriol> q+<br> <astearns> ack SebastianZ<br> <ydaniv> SebastianZ: quick idea, maybe introduce keywords><br> <ydaniv> s/>/?/<br> <astearns> ack oriol<br> <fantasai> SebastianZ: e.g. "1 to 6"<br> <ydaniv> oriol: no strong opinion<br> <TabAtkins> If you want *all* headings, that's `:heading`. if you want several but not all, `:heading(1, 2, 3, 4, 5)` isn't bad to write<br> <ydaniv> ... however, if we go with list the stack should be using logical OR or AND<br> <fantasai> TabAtkins: Not possible to have something be both heading 1 and heading 2,<br> <fantasai> TabAtkins: so only one possible interpretation<br> <ydaniv> florian: I think we should go with list of integers, just to clarify<br> <lea> Q?<br> <ydaniv> SebastianZ: advocate for using just numbers, but allow patterns?<br> <ydaniv> florian: not object but seems unnecessary<br> <ydaniv> fantasai: Agree with florian, we shouldn't bother<br> <kbabbitt> +1 to florian<br> <ydaniv> +1 to florian<br> <TabAtkins> +1<br> <ydaniv> PROPOSED: use comma separated integers<br> <lea> Q+<br> <ydaniv> astearns: other comments?<br> <ydaniv> lea: the An+B case is one of the comlex cases, something that also come with nth-child case<br> <astearns> ack lea<br> <ydaniv> ... and authors have to write all sorts of weird things<br> <ydaniv> ... so instead of just commas is to allow ranges from a to b<br> <ydaniv> TabAtkins: argument against is because the set is finite then allow just specifying it<br> <ydaniv> lea: in this case yes, because it's finite<br> <ydaniv> ... in other cases ranges are more desirable<br> <ydaniv> ... then we can also fix it here and fix all<br> <florian> q+<br> <astearns> ack fantasai<br> <ydaniv> fantasai: don't disagree, but think this is not the place to fix it<br> <ydaniv> lea: it's already limited to integers<br> <SebastianZ> lea See https://github.com/w3c/csswg-drafts/issues/4140<br> <kizu> To crosslink stuff, SebastianZ's issue about ranges: https://github.com/w3c/csswg-drafts/issues/4140<br> <ydaniv> lea: I agree we should simplify, but think we also need ranges<br> <TabAtkins> fantasai: people don't do repeating patterns on hierarchical section levels<br> <ydaniv> astearns: we're not going to discuss ranges for this issue<br> <ydaniv> ... was brought up before, but not for this one<br> <ydaniv> florian: I think choice should be either list of integers, or straight to An+B as a list<br> <ydaniv> ... I think there's one impl. in ladybird?<br> <ydaniv> ... if we haven't specced or implemented anything then <missed><br> <ydaniv> ... if it's done already then, I'm ok with list of integers<br> <emilio> q+<br> <florian> s/f we haven't specced or implemented anything then <missed>/f we hdn't specced or implemented anything then I'd to list of integers<br> <ydaniv> astearns: we have 2 options? currently has a list of An+B, we can leave like that or change to list of integers<br> <astearns> ack florian<br> <astearns> ack emilio<br> <ydaniv> emilio: we can change have way<br> <florian> s/if it's done already then, I'm ok with list of integers/given that it's already implemmented in a few places, I'm ok with list of An+Bs<br> <ydaniv> ... I don't think having a list of integers is the only thing we could do<br> <ydaniv> astearns: hearing slight preference to list of integers<br> <ydaniv> emilio: might save a couple of bytes<br> <ydaniv> SebastianZ: once we discuss the issue about ranges and come to a solution on that<br> <ydaniv> ... I would apply that to all the other places<br> <ydaniv> florian: but that remains open regardless<br> <ydaniv> ... we're still open to doing that<br> <astearns> 1) list of An+B 2) list of integers<br> <TabAtkins> 2<br> <ydaniv> astearns: let's draw a poll<br> <fantasai> 2, but also ok with 1<br> <kbabbitt> 2<br> <lea> 2<br> <andruud> 2<br> <astearns> no preference<br> <emilio> weak preference for 1, also fine with 1<br> <SebastianZ> No preference<br> <diekus> 2<br> <oriol> abstain<br> <emilio> with 2*<br> <alisonmaher> No preference<br> <kizu> 2<br> <ydaniv> 2<br> <florian> ok either way<br> <ydaniv> proposed resolution: change spec to list of integers<br> <ydaniv> astearns: objections?<br> <ydaniv> RESOLVED: change spec to list of integers<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12599#issuecomment-3209671569 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 09:10:05 UTC