- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Nov 2023 23:30:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-grid-3] Repeat range`, and agreed to the following: * `RESOLVED: Add two numbers to the repeat function that when used with one of the keywords define a range` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> +1 to the proposal, and to making the keyword optional if numbers are given (defaulting to auto-fill)<br> <dael> fantasai: Another issue iank_ brought up is desire to have repetition, example 3 to 5 instead of exactly 5. Seemed useful for grid regardless of masonary. Opened issue to propse repeat syntax that covers a range. It would be autofill or autofit with one or two numbers. If two, first is min and second is max. If you only give one it's a max.<br> <dael> fantasai: One is a max is consistent with how we do multicol. And consistent that main problem is too narrow, not too wide<br> <oriol> q+<br> <dael> fantasai: Syntax is reorderable b/c generally want to allow reordering unless parsing reason not to<br> <astearns> ack oriol<br> <dael> oriol: It seems reasonable to me to be able to spec a min with no max. I guess you could do it was calc 1/0 to get infinity. Should we add a way to spec min?<br> <dael> fantasai: You can spec infinity as a keyword. You can spec a keyword for no ax<br> <dael> TabAtkins: I agree makes sense to allow unspecified as max so keyword makes sense<br> <dael> fantasai: keyword like nomax?<br> <dael> TabAtkins: Should go with infinity. Or infinite.<br> <fantasai> s/nomax/no-max/<br> <dael> fantasai: Okay, that's in animation. good to be consistent<br> <dael> astearns: If you have a repeat that's repeat(autofill 3) it's a max but if you add infinite keyword the 3 is the minimum<br> <dael> fantasai: If you add a 5 the minimum is 3.<br> <dael> TabAtkins: Having consistently the first number be the min isn't problematic and you can always add a max<br> <dael> fantasai: I don't think we want to do that becase columns we do that as a maximum<br> <dael> astearns: Question do we require 2 numbers<br> <dael> TabAtkins: IN concat can we do min and max?<br> <dael> fantasai: Just a max<br> <dael> TabAtkins: Then I think more comfortable requiring 2<br> <TabAtkins> s/concat/column-count/<br> <dael> fantasai: I could live with that.<br> <dael> fantasai: I think it would be nice to have the one, but if we want to require we can do that<br> <dael> astearns: We can start with both and when there's author experience decide if we want to allow a single<br> <dael> astearns: One question...you talk about this is important for masonary, but also important for non-masonary<br> <dael> 3?<br> <dael> fantasai:<br> <dael> Yes. Prop is add to grid properties to effect both<br> <fantasai> s/effect/affect/<br> <dael> astearns: And we don't have a repeat function?<br> <dael> fantasai: Repeat can take number or a keyword. This allows you to combine both to get a range<br> <TabAtkins> i forgot that we could take a number by itself. in that case i definitely think the range should require both<br> <dael> astearns: Prop: Add two numbers to the repeat function that when used with one of the keywords define a range<br> <dael> astearns: Obj?<br> <dael> RESOLVED: Add two numbers to the repeat function that when used with one of the keywords define a range<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9325#issuecomment-1789830378 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 November 2023 23:30:20 UTC