Chromium lands Flexbox gap

The CSS gap property is here for Chromium's CSS Flexbox and Multi-Column layout engines.

May 7, 2020 — Updated Jun 19, 2020

Adam Argyle

TwitterGitHubGlitchHomepage

David Grogan

GitHub

CSS Gap #

gap is flow relative, meaning it changes dynamically based on the direction of content flow. For example, gap will automatically adjust for the different writing-mode or direction values that you set for your international users. This significantly eases the burden of spacing challenges for the component and CSS author. Less code scaling further.

Browser compatibility #

Usage #

gap accepts any CSS length or percentage as a value.

.gap-example {
  display: grid;
  gap: 10px;
  gap: 2ch;
  gap: 5%;
  gap: 1em;
  gap: 3vmax;
}

Gap can be passed 1 length, which will be used for both row and column.

.grid {
  display: grid;
  gap: 10px;
}

.grid {
  display: grid;
  row-gap: 10px;
  column-gap: 10px;
}

Gap can be passed 2 lengths, which will be used for row and column.

.grid {
  display: grid;
  gap: 10px 5%;
}

.grid {
  display: grid;
  row-gap: 10px;
  column-gap: 5%;
}

Flexbox gap #

Before gap was in Flexbox, strategies involved negative margins, complex selectors, :last or :first type pseudo-class selectors, or other means to manage the space of a dynamically layed-out and wrapping set of children.

Previous Attempts #

The following are patterns that folks have used to get gap-like spacing.

.layout > :not(:last-child) {
  margin-bottom: 10px;
  margin-right: 10px;
}

.layout > * + * {
  margin-bottom: 10px;
  margin-right: 10px;
}

The above are not a full replacement for gap though, and often need @media or :lang() adjustments to account for wrapping scenarios, writing modes or direction. Adding one or two media queries doesn't seem so bad, but they can add up and lead to complicated layout logic.

What the above author really intended was to have none of the child items touch.

The Antidote: gap #

.layout {
  display: flex;
  gap: 10px;
}

In the first 2 examples (without Flexbox gap), the children are targeted and assigned spacing from other elements. In the antidote gap example, the container owns the spacing. Each child can relieve itself of the burden, while also centralizing the spacing ownership. Simplifying consistency. Reorder, change viewports, remove elements, append new elements, etc. and spacing remains consistent. No new selectors, no new media queries, just space.

Chromium DevTools updates #

With these updates come changes to Chromium DevTools, notice how the Styles pane handles grid-gap and gap now 👍