- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Nov 2017 20:16:52 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `"Equal Gutter" with justify-content`. <details><summary>The full IRC log of that discussion</summary> <frremy> Topic: "Equal Gutter" with justify-content<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/1116<br> <frremy> fantasai: users often want row-gaps and col-gaps to be equal<br> <frremy> fantasai: but they also want the horizontal gaps to fill the remaining space once you've put as many columns as possible in the width direction<br> <frremy> fantasai: they can do that using justify-content<br> <frremy> fantasai: but they cannot transfer this size in the other direction<br> <frremy> fantasai: this is basically a request for thoughts on the topic<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/1116#issuecomment-288472394<br> <fantasai> Just to summarize, the example is<br> <fantasai> definite width, auto height grid container<br> <fantasai> auto-fill columns e.g. 100px<br> <fantasai> auto-placed items<br> <fantasai> place-content: space-between<br> <fantasai> The spacing produced by space-between is not equal in both axes.<br> <frremy> jensimmons: so is the idea { row-gap: as-column-gap }<br> <frremy> jensimmons: ?<br> <frremy> TabAtkins: pretty much<br> <frremy> (general discussion, but it was thought to minute)<br> <TabAtkins> s/thought/tough/<br> <frremy> fantasai: the tricky thing is that two things control the gap size<br> <frremy> fantasai: the gap property<br> <frremy> fantasai: and the alignment properties<br> <frremy> fantasai: you do have to consider both to get the desired effect<br> <frremy> fantasai: and there are interersting cases of space-evenly which creates a gap before the first column and after the last column, we will need to define what to do about that<br> <fantasai> the gap properties only distribute space between the columns, but alignment can do other things<br> <frremy> florian: and the proposed syntax would allow to also define alignment in the direction in which you said to copy<br> <frremy> florian: I think we should have a more restrictive syntax that doesn't allow the impossible cases would be better<br> <frremy> florian: but I don't have a concrete proposal right now<br> <frremy> jensimmons: just to clarify, the alignment do not update the gap, they add a gutter right?<br> <frremy> fantasai: yes, but visually it looks like the same thing<br> <frremy> jensimmons: so it looks like we want something to transfer the gutter not the gap<br> <frremy> dholbert: maybe some align: symmetrical then?<br> <frremy> dholbert: alignment properties already are allowed to increase a gap<br> <frremy> dholbert: it would be possible to also shrink the gap to make it match, that doesn't sound unreasonable<br> <dholbert> Or possibly not shrink, but grow-or-leave-the-same (to avoid)<br> <frremy> Rossen: alright, I think we should probably break out to lunch, and have people interested in this proposal talk with each other<br> <frremy> Rossen: let's get back here at 1.30<br> <dholbert> *(to avoid violating author expectations that "grid-row-gap: 100px" should actually insert at least 100px of space)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1116#issuecomment-342272800 using your GitHub account
Received on Monday, 6 November 2017 20:16:55 UTC