We discussed on the mailing list (pre-github) having a -gap property that works like column-gap for multi-col, and the CSS Grid grid-gap properties. It seems that this would solve this issue?

https://lists.w3.org/Archives/Public/www-style/2016Feb/0333.html

@rachelandrew Yes, that would probably cover most use-cases.

You'd want to be able to set both a column gap and a row gap, and then spacing between flex items should never shrink below that. If any items needed additional or different margin, the regular margin properties would still apply.

I would also really like to see this.

@AmeliaBR I came up with an alternative to the negative margin hack, which instead uses padding inside the flex items: https://oliverjash.me/2016/12/28/gutters-for-flexible-components-with-sliced-padding

Some sort of gutter/gap property would likely result in code that is much easier to read and maintain.

I agree flex-gap is desperately needed.

I think the lack of such a tool is part of why people struggle with Flexbox. It's common for an author to want to specify a minimum or fixed amount of space between items, and it's confusing to not be sure how we are “supposed to” accomplish such a thing. Margins and padding exist, of course, but they are old dependancies stuck in the midst of a new and better system. It feels like there is supposed to be a new better way to create and control a gap between items.

I’m definitely in favor of adding flex-gap or similar to flexbox. I feel like many cases where flex gaps might be used would be at least as well served by using grid and its gaps, but by no means every case.

For reference, an example of this question being asked in the wild (May 2014): http://stackoverflow.com/questions/23433436/spacing-between-flexbox-items

This would be a tremendously useful addition and a perfect solution to the problem!

In my mind there are currently 2 approaches to multiline flexbox grids:

1. As @AmeliaBR said Grid containers with negative left margins and grid items with left padding. The issue with this method is that if you need to add padding to a grid item you have to nest an element within it and style that.

2. Omega/last classes. The issue with this method is that for multiline grids you must write a class where the content should end on each line and you end up controlling layout within your application logic. e.g. if($i = 4){ echo 'item--last' };

flex-gap would prevent these 2 different but equally inelegant solutions in favour of something maintainable and understandable.

As flex rightly replaces table-* rules for layout, I would appreciate a non-hacky (i.e., not requiring additional, non-semantic markup or relying on inconsistent browser behaviors), meaningfully readable way to provide gutters or gaps between flex items.

I support the proposal for a flex-specific margin property that overrides the regular margin in the flex-direction and has a space-around vs space-between option. This would be incredibly useful.

Is there a use case for it being available on the cross axis as well as the main axis? It feels like that would be useful but I can't think of a concrete example at this moment.

Definitely saw some use-cases for this, if it's similar to grid-gap even better (less learning)!

I for one would love to see a flex-gap property. It should behave in the same way as the grid-gap property.

Rather than a flex- prefixed property, I would like to see a normalized property name to handle gutter definitions for columns, flex containers, and grid containers. This seems logical considering how align- and justify- properties have currently been implemented for grid.

item-gap perhaps?

example {
  display: flex;
  item-gap: 1rem;
}

example {
  display: grid;
  item-gap: 1rem;
}

example {
  columns: 4;
  item-gap: 1rem;
}

I agree, something like flex-grid would help cut down on extra containers or hacks we may have to do.

It might be more useful if we can specify a min/max gap to have more control over the layout of the items.

I was thinking about this recently, before I saw this thread. My thought was that there should be something like 'margin-between' that changed the computed values of margin-*. So, margin-between-x would change horizontal margins (but not the left margin of the leftmost items or the right margin of the rightmost items). margin-between-y would work similarly for vertical. Margin-between-inline and margin-between-block would be even better.

This is needed for things other than flex, such as a series of inline-block items on one or more lines. It is needed in horizontal and vertical. And it would benefit from normal margin collapsing, when some items on the line didn't have margin-between, but had some other margin.

I've needed this since before I ever started using flexbox.

This just came up again when talking about margin collapsing in #1324 (and that margin collapsing and gaps between flex items are two different things).

@erikjung's suggested generally applying item-gap sounds good to me. grid-gap needs to be turned into an alias for it, then, though. And there also need to be general equivalents for grid-row-gap and grid-column-gap, e.g. item-gap-block and item-gap-inline.

Sebastian

@SebastianZ wouldn't it be more explicit to state what 'thing' the gap is for? It seems more obvious to me. i.e. flex-gap& grid-gap rather than a single item-gap for everything, e.g. what if they need to be different at some point in the future?

@morganfeeney Good point! Though I think it's obvious enough to what item-gap refers to. It might be even more obvious if there were a columns value for the display property to control whether the column-* properties apply. That would make item-gap always refer to the display type.

Sebastian

I've split out my idea about a display: columns; value into issue #1352, so it can be discussed separately.

Sebastian

The CSSWG resolved to switch Grid to using generic row-gap and column-gap properties, and to expand these to affect Flexbox. See #1696

I'm going to close this issue as fixed; please file a new issue if there's something else to be considered here. :) Thanks everyone~