- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 18 Mar 2026 15:59:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-gaps-1]: Assigning multiple decoration values to flex containers`. <details><summary>The full IRC log of that discussion</summary> <hoch> oSamDavis: The width value accepts multiple values. How should they apply to cross-gaps in flex?<br> <hoch> oSamDavis: Option 1 is to go linearly. Option 2 is to reset at every line.<br> <kbabbitt> q+<br> <hoch> oSamDavis: I prefer the linear assignment. It's more intuitive. It doesn't require math to figure out the line.<br> <astearns> ack kbabbitt<br> <hoch> kbabbitt: My initial reaction was that it would restart for consistency with grid. I can see the argument for it being a linear assignment across the container.<br> <hoch> kbabbitt: Another thing we should consider is the multi-col behavior.<br> <astearns> ack fantasai<br> <hoch> fantasai: I think multi-col should follow the grid model of resetting on every row.<br> <hoch> fantasai: For flex, the distinction is on the use case. Usually it's "here's a pile of items", but sometimes you use it for a toolbar with particular ordering.<br> <hoch> fantasai: So I can see use-cases for both.<br> <hoch> fantasai: So I think we need more input from authors to see which way this should go.<br> <davidjmarland> q+<br> <hoch> fantasai: You don't want multi-col to change based on how many columns you ended up with.<br> <astearns> ack davidjmarland<br> <hoch> davidjmarland: I do agree with the concept of resetting on every row.<br> <hoch> davidjmarland: If you had one item offset the gaps, that would make them no longer line up though.<br> <hoch> <discussion on how this isn't a concern for grid, just for flex><br> <hoch> astearns: When Sam Davis originally presented this I though single line would be the normal case. And might associate items with colors. And when you have an unexpected break in the line that would throw it off. But I'm having trouble coming up with a strong position either way.<br> <hoch> astearns: Could we resolve on resetting per line in all of the layout contexts?<br> <hoch> astearns: And add a new keyword later if we need to support a linear approach in flex?<br> <hoch> oSamDavis: I would still lean on the linear approach. If the argument is flex is grid like, I would argue it's fundamentally different.<br> <hoch> oSamDavis: I don't know about other web devs.<br> <kbabbitt> q+<br> <hoch> astearns: I agree, but one of the things we keep hearing is a desire to have per-line control over things.<br> <hoch> alisonmaher: The most common case is likely 2 colors (e.g. black and white) and resetting could make sense in that case.<br> <hoch> kbabbitt: If we wanted to add an author toggle in the future based on feedback. Is one behavior or the other easier to achieve backwards compatability?<br> <hoch> alisonmaher: If we have the same default across all of them that would probably work best. But we could always add an 'auto' or 'normal'.<br> <hoch> oSamDavis: We can resolve on the per-line reset, and in the future explore making it more global.<br> <hoch> fantasai: We should ask people to comment on in the main call, and go back to the DevRel team.<br> <hoch> astearns: So leave this issue open, and come back to it soon for a resolution.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13663#issuecomment-4083682660 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 March 2026 15:59:49 UTC