Title: CSS Grid Layout Module Level 3
Shortname: css-grid
Level: 3
Status: ED
Work Status: Exploring
Group: csswg
TR:  https://www.w3.org/TR/css-grid-3/
ED: https://drafts.csswg.org/css-grid-3/
Editor: Tab Atkins Jr., Google, http://www.xanthir.com/contact/, w3cid 42199
Editor: Elika J. Etemad / fantasai, Apple, http://fantasai.inkedblade.net/contact, w3cid 35400
Former Editor: Mats Palmgren, Mozilla, mailto:mats@mozilla.com
Editor: Jen Simmons, Apple, http://jensimmons.com/, w3cid 52801
Editor: Brandon Stewart, Apple, https://brandonstewart.net, w3cid 138640
Abstract: This module introduces masonry layout as an additional layout mode for CSS Grid containers.
WPT Path Prefix: css/css-grid/masonry/tentative/
WPT Display: open
Markup Shorthands: css yes
Status Text: This specification represents two variations on the proposal for masonry layout. Feedback on the alternatives is welcome.

Introduction

This section is not normative. Grid Layout is a layout model for CSS that has powerful abilities to control the sizing and positioning of boxes and their contents. Grid Layout is optimized for 2-dimensional layouts: those in which alignment of content is desired in both dimensions.
An example of grid layout:
		     two rows of items,
		     the first being four items — the last of which spans both rows,
		     and the second being two items —
		     the first of which spans the first two columns —
		     plus the spanned item from the first row.
Representative Grid layout example
Although many layouts can be expressed with regular Grid Layout, restricting items into a grid in both axes also makes it impossible to express some common layouts on the Web. This module defines a layout system that removes that restriction so that items can be placed into Grid-like tracks in just one of the axes, while stacking them one after another in the other axis. Items are placed into the column (or row) with the most remaining space based on the layout size of the items placed so far. This module also extends CSS Grid with this new grid item placement strategy and CSS Box Alignment with new alignment features.

Background and Motivation

Waterfall Layout with Auto-placed Items

[=Masonry layout=], sometimes also called “waterfall layout”, is a common Web design pattern where a number of items-- commonly images or short article summaries-- are placed one by one into columns in a way that loosely resembles stone masonry. Unlike [[CSS-MULTICOL-1|multi-column layout]], where content is placed vertically in the first column until it must spills over to the second column, [=masonry layout=] selects a column for each new item such that it is generally closer to the top of the layout than items placed later.
The Pinterest search results page exemplifies this layout:
An example of masonry layout:
			          four columns of items,
			          each item is placed into the column with the smallest height so far.
Representative masonry layout example
Here, each item has a different height (depending on the content and the width of the column), and inspecting the DOM reveals (as the visual content itself gives no indication of ordering) that each item has been placed into the column with the smallest height so far.
This layout superficially looks similar to multi-column layout; but it has the advantage that scrolling down will naturally lead to "later" items in the layout (that is, those less relevant in the search results). It's not possible to achieve this layout using earlier CSS layout models, unless you know up-front how tall each item will be, or use JavaScript for content measurement or placement. Using a [=masonry container=] together with ''grid-area/auto''-positioned items yields this type of masonry layout.

One-dimensional Grid Layout

[=Grid layout=] allows for powerful track sizing and explicit placement in two axes, but sometimes a layout only needs alignment of its items in one dimension. Using a [=masonry container=] together with explicitly-positioned items allows for this type of one-dimensional grid layout.
This example by Douglas Graham uses explicit positioning to place each item into its assigned column; but there are no rows. Instead, items in each column stack one after the other. This layout can't be duplicated in [=grid layout=] because the “spanning” relationships among the items in adjacent columns is not fixed: it depends on their relative heights and whether the optional banner or advertisement items are included. It also can't be duplicated in [=flex layout=] because the source order of the items (which is used for reading, sequential navigation, and one-column mobile phone layout) goes back and forth between the two columns.
In one-column layout:
			          the header, followed by an optional banner, the secondary navigation,
			          the main content area, an advertisement block, and finally the footer.
			          In two-column layout:
			          the header spanning both columns on top,
			          the footer spanning both columns at the bottom,
			          in the wider left column the optional banner followed by the main content area,
			          and in the narrow left column the secondary navigation followed by the advertisement block.
Comparison of one-column and two-column variants of a one-dimensional grid layout.

Alternative Syntax Proposals

The masonry layout feature of this specification is drafted with two different syntaxes to promote debate and discussion of these two alternatives.
Grid-integrated Option
In this syntax model, [=masonry layout=] is integrated into the [=grid layout=] model, re-using all of the 'grid-*' properties.
Grid-independent Option
In this syntax model, [=masonry layout=] is its own 'display' type, and has its own parallel set of 'masonry-*' properties.

Value Definitions

This specification follows the CSS property definition conventions from [[!CSS2]] using the value definition syntax from [[!CSS-VALUES-3]]. Value types not defined in this specification are defined in CSS Values & Units [[!CSS-VALUES-3]]. Combination with other CSS modules may expand the definitions of these value types. In addition to the property-specific values listed in their definitions, all properties defined in this specification also accept the CSS-wide keywords as their property value. For readability they have not been repeated explicitly.

Masonry Layout Model

Masonry layout lays out items into pre-defined tracks similar to [=grid layout=] in one axis (called the grid axis), but flows them freely similar to [=flex layout=] in the other (called the stacking axis). Similar to [=grid layout=] and unlike [=flex layout=], [=masonry layout=]’s auto-placement distributes items across the tracks to keep the lengths of those tracks as similar as possible. [=Grid items=] are formed and [=blockified=] exactly the same as in a regular [=grid container=]. (For clarity, [=grid items=] and [=grid tracks=] of a [=masonry container=] can be referred to as masonry items and masonry tracks.) All CSS properties work the same as in a regular [=grid container=] unless otherwise specified by this specification. For example, 'order' can be used to specify a different layout order for the items. Note: Subgrid items are supported, but subgridding only occurs in the [=grid axis=]; see [[#subgrids]] for details. A masonry container is a box whose contents participate in [=masonry layout=]. A [=masonry container=] is a column masonry container if its [=stacking axis=] is the [=block axis=], or a row masonry container if its [=stacking axis=] is the [=inline axis=].
Establishing Masonry Containers
Grid-integrated Syntax Grid-independent Syntax Description
Column Masonry
					display: grid;
					grid-template-columns: 1fr 2fr 3fr;
					grid-template-rows: masonry;
				
					display: masonry;
					masonry-tracks: 1fr 2fr 3fr;
					masonry-direction: column;
				
Column masonry lays out items in columns,
					     but ordered across the columns,
					     placing each item in the then-shortest column.
Row Masonry
					display: grid;
					grid-template-rows: 1fr 2fr 3fr;
					grid-template-columns: masonry;
				
					display: masonry;
					masonry-tracks: 1fr 2fr 3fr;
					masonry-direction: row;
				
Row masonry lays out items in rows,
					     but ordered down across the rows,
					     placing each item in the then-shortest row.

Reordering and Accessibility

Although [=masonry layout=] generally progresses in a forwards fashion (placing the next item down or endward of the current item, matching the natural "reading order"), it can switch between these two in a seemingly arbitrary manner. In simple cases, the 'masonry-slack' property can help reduce the feeling of backtracking due to small sizing differences in the [=block axis=] when laying out auto-placed items. But when [[#masonry-layout-algorithm|auto-placement]] is mixed with [=definite position|explicit placement=] or spanning items, some amount of backtracking may occur.
For example, in the following markup sample, the fourth item is a spanner that doesn't fit in the remaining empty column on the first line. It ends up positioned into the into the first column, which is the highest available space into which it will fit. The next few items, which have a span of 1, end up laying out “above” it in the empty column, violating the natural reading order. <section class=masonry> <div class=item>1</div> <div class=item>2</div> <div class="item tall">3</div> <div class="item wide">4</div> <div class=item>5</div> <div class=item>6/div> <div class=item>7</div> </section> <style> .masonry { display: masonry; masonry-tracks: repeat(5, auto); } .item { height: 50px; } .item.wide { masonry-track: span 3; } .item.tall { height: 90px; } </style>
In this example, the first row is items 1, 2, 3, 5, 6,
			          with item 3 slightly taller than the others.
			          Item 4 spans the first three columns, and is placed
			          just below item 3, while item 7 is tucked under item 5.
Auto-placed masonry layout with mixed-height items and mixed span sizes
Similarly, items explicitly placed into specific tracks can leave gaps behind them, into which subsequent auto-placed items can be placed visually out-of-order.
Authors should be aware of these possibilities and design layouts where such backtracking is minimized so that focus and reading order can be more easily followed. Alternatively, if the items do not have an inherent order, use the 'reading-flow' property to allow the UA to re-order the items for reading and linear navigation. ISSUE: Or should reordering be the default behavior for auto-placed items here?
Techniques for reducing backtracking include: * Using appropriate values for 'masonry-slack', i.e. values large enough to avoid gratuitous differentiation among similarly-sized tracks, but not so large that meaningful differences get ignored. * Using explicit placement in ways that help group related items together, rather than ways that disrupt the natural order of items * Avoiding the combination of mixed span sizes in the [=grid axis=] and disparate item sizes in the [=stacking axis=], which can cause items to get pulled out of order (see example above).
As with [=grid layout=] and [=flex layout=] authors can use the 'order' property to re-order items; the same caveats apply. See [[css-grid-2#order-accessibility]] and [[css-flexbox-1#order-accessibility]].

Grid-integrated Option: Establishing Masonry Layout

Indicating the stacking axis: the ''grid-template-columns/masonry'' keyword for 'grid-template-columns'/'grid-template-rows'

		Name: grid-template-columns, grid-template-rows
		New values: masonry
		Initial: none
		Applies to: [=grid containers=]
		Inherited: no
		Percentages: refer to corresponding dimension of the content area
		Computed value: the keyword ''grid-template-columns/none'' or the keyword ''grid-template-columns/masonry'' or a [[computed track list]]
		Animation type: see [[css-grid-2#track-sizing|CSS Grid Level 2]]
	
[=Masonry layout=] can be applied to [=grid containers=] by specifying the value ''grid-template-columns/masonry'' for one of its axes, defining it as the [=stacking axis=]. Such [=grid containers=] are called [=masonry containers=]. If ''grid-template-columns/masonry'' is specified for both ''grid-template-columns'' and ''grid-template-rows'', then the [=used value=] for ''grid-template-columns'' is ''grid-template-columns/none'', and thus the [=inline axis=] will be the [=grid axis=].

Auto Flow Directions: the 'grid-auto-flow' property

	Name: grid-auto-flow
	Value: [ row | column | row-reverse | column-reverse ] || dense || wrap-reverse
	Initial: row
	Applies to: grid containers
	Inherited: no
	Percentages: n/a
	Computed value: specified keyword(s)
	Animation type: discrete
	

This specification extends the grid-auto-flow property to add row-reverse, column-reverse, and wrap-reverse, which reverse the directions of the [=grid item placement algorithm=]. In [=masonry layout=], the flow axis specified by ''grid-auto-flow'' is ignored: items are always placed by filling across the [=grid axis=]. ISSUE: Should that be the case, or should we follow the 'grid-auto-flow' axis always (so it would fill similar to flexbox, but with explicitly-sized tracks)? ISSUE(9326): Should dense packing apply to masonry? It's much more expensive in masonry, as you have to lay out the element in every possible gap spot to see if it's short enough to fit; Grid gets to just juggle some integers.

Grid-independent Option: Establishing Masonry Layout

Establishing Masonry Containers: the ''masonry'' and ''inline-masonry'' 'display' values

	Name: display
	New values: masonry | inline-masonry
	
: masonry :: This value causes an element to generate a [=masonry container=] box that is [=block-level=] when placed in [=flow layout=]. : inline-masonry :: This value causes an element to generate a [=masonry container=] box that is [=inline-level=] when placed in [=flow layout=].

Masonry Track Direction: the 'masonry-direction' property

	Name: masonry-direction
	Value: row | column | row-reverse | column-reverse
	Initial: column
	Inherited: no
	Applies to: [=masonry containers=]
	Computed value: as specified
	Animation type: discrete
	
The 'masonry-direction' property specifies how items are placed in the [=masonry container=], by setting its [=stacking axis=] and direction.
: column :: The [=masonry container's=] [=stacking axis=] is its [=block axis=], and masonry layout starts from its [=block-start=] edge. : column-reverse :: The [=masonry container's=] [=stacking axis=] is its [=block axis=], and masonry layout starts from its [=block-end=] edge. : row :: The [=masonry container's=] [=stacking axis=] is its [=inline axis=], and masonry layout starts from its [=inline-start=] edge. : row-reverse :: The [=masonry container's=] [=stacking axis=] is its [=inline axis=], and masonry layout starts from its [=inline-end=] edge.
The [=masonry container's=] [=grid axis=] is perpendicular to its [=stacking axis=].

Masonry Cross Direction: the 'masonry-fill' property

	Name: masonry-fill
	Value: normal | reverse
	Initial: normal
	Inherited: no
	Applies to: [=masonry containers=]
	Computed value: as specified
	Animation type: discrete
	
'masonry-fill' determines what direction auto-placed items are laid out in when multiple tracks are tied for “shortest”.
: normal :: Ties are broken by filling the startmost track : reverse :: Ties are broken by filling the endmost track.

Masonry Flow Directions: the 'masonry-flow' shorthand

	Name: masonry-flow
	Value: <<'masonry-direction'>> || <<'masonry-fill'>>
	
The 'masonry-flow' property is a [=shorthand=] for the 'masonry-direction' and 'masonry-fill' properties.

Masonry Definition Shorthand: the 'masonry' property

Name: masonry
Value: <<'masonry-template-areas'>> || <<'masonry-template-tracks'>> || <<'masonry-direction'>> || <<'masonry-fill'>>
The 'masonry' shorthand sets 'masonry-template-areas', 'masonry-template-tracks', 'masonry-direction', and 'masonry-fill' at the same time.

Masonry Track Specification

In the [=grid axis=], the full power of [=grid layout=] is available for track specification: * Track sizes, line names, and areas can be specified on the [=masonry container=]’s [=grid axis=], just like in [=grid layout=]. * The [=explicit grid=] and [=implicit grid=] are formed in the same way as for a regular [=grid container=]. * Items can be [[#masonry-track-placement|placed]] against these grid templates just as in [=grid layout=]. However, auto-placed items contribute sizing to all tracks, not just the track into which they are ultimately placed; see [[#track-sizing]]. Note: This is because auto-placed items must be laid out as they are placed, so that each track knows how “full” it is (and therefore which track should receive the next auto-placed item); thus, the tracks themselves must already have a definite size so that the items know their [=available space=] during layout.

Grid-integrated Option: Declaring Masonry Track Templates: the 'grid-template-*' properties

The 'grid-template-*' and 'grid-auto-rows'/'grid-auto-columns' properties (and their shorthands) apply in the [=grid axis=] of the [=masonry container=] and establish tracks just as on regular [=grid containers=]. ISSUE(10869): What should be the initial track listing?

Grid-independent Option: Declaring Masonry Track Templates: the 'masonry-template-*' properties

Tracks in the [=grid axis=] of a [=masonry container=] are established with 'masonry-template-tracks', 'masonry-template-areas', and 'masonry-auto-tracks'.
	Name: masonry-template-tracks
	Value: none | <> | <> | subgrid <>?
	Initial: repeat(auto-areas, auto)
	Applies to: [=masonry containers=]
	Inherited: no
	Percentages: refer to corresponding dimension of the content area
	Computed value: by computed value type per item in the [=computed track list=]
	Animation type: if list lengths match, by [=computed value=] type; otherwise, discrete
	
The syntax of 'masonry-template-tracks' is a superset of 'grid-template-columns'; all shared values have identical interpretations. (The additional values are that <>, unlike <> in 'grid-template-columns', allows intrinsic sizes to be combined with auto repetition; see [[#masonry-intrinsic-repeat]] for details.) It also has a different initial value: ''repeat(auto-areas, auto)'' rather than ''grid-template-columns/none''. ISSUE(10869): What should be the initial value?
		<masonry-auto-track-list> = [ <>? [ <> | <> ] ]*
		                            <>? <> <>?
		                            [ [ <> | <> ] <>? ]*
	
	Name: masonry-template-areas
	Value: none | <>
	Initial: none
	Applies to: [=masonry containers=]
	Inherited: no
	Percentages: n/a
	Computed Value: the keyword ''masonry-template-values/none'' or a string
	Canonical Order: per grammar
	Animation type: discrete
	
'masonry-template-areas' has the same syntax and interpretation as 'grid-template-areas', except it only takes a single string defining one "row" of area names.
	Name: masonry-auto-tracks
	Value: <<'grid-auto-columns'>>
	Initial: auto
	Applies to: grid containers
	Inherited: no
	Percentages: refer to corresponding dimension of the content area
	Computed value: a [=computed track list=]
	Canonical order: per grammar
	Animation type:	if the list lengths match, by computed value type per item; discrete otherwise
	
'masonry-auto-tracks' has the same syntax and interpretation as 'grid-auto-columns'.

Intrinsic Tracks and repeat()

ISSUE(10915): Should we allow auto-repeated content-based tracks? Is this a reasonable definition for them? Should they work also in Grid Layout somehow? In Grid Layout, all [=grid items=] are placed in the grid before the grid tracks are sized. This implies that ''repeat()/auto-fill''/''repeat()/auto-fit'' repetition can't include intrinsically sized tracks such as ''grid-template-rows/auto'' (either in the ''repeat()'' function or alongside it in the fixed portion of the track list), as that would require the layout algorithm to have already determined which items would go in those tracks, to determine how large the tracks are, to determine how many repetitions fit in the available space. In Masonry Layout, as [=masonry item=] placement and layout are intertwined and somewhat simplified, this restriction is no longer strictly required. It requires a slightly heuristic definition of sizing, but auto repetition can include intrinsically-sized tracks in a [=masonry container=] (and the initial value of 'masonry-template-tracks' uses this!).
To determine the number of repetitions that a ''repeat()'' function resolves to, run layout as defined in [[#track-sizing-performance]], with the following changes: * Expand ''repeat()/auto-fill''/''repeat()/auto-fit'' repeat functions once. * Ignore item placement. (That is, assume all items have ''masonry-track: auto''.) * If a [=masonry item=] has a span larger than 1, then for each of its intrinsic sizes that it would contribute to the [=virtual masonry item=], first subtract the combined size of the gaps it would span, and divide by its span. Then treat it as being a span-1 item with those sizes. Any intrinsically-sized tracks are then treated as having the size calculated by this simplified layout (including those in ''repeat()'' arguments, taking from their corresponding single repetition) for the purpose of determining how many repetitions the ''repeat()'' functions resolve to.
Motivation This simplified layout heuristic is defined to be "good enough", while remaining fast and consistent. Ignoring placement is required just to make the concept coherent; before you know how many repetitions you need, you can't tell what track an item with a definite placement will end up in. By chopping spanning items into span-1 items, this avoids the possible need to expand a repeat() multiple times, and the incoherent possibility of getting different sizes for the same keyword across the repetitions. It also makes the layout as a whole significantly cheaper, as you only need to consider each unique track size; you don't even really need to do any repeat() expansion. That is, in ''auto repeat(auto-fill, min-content auto)'', both of the ''grid-template-rows/auto'' keywords will resolve to the same size under this heuristic layout; you can just figure out what a ''masonry-template-tracks: auto'' and ''masonry-template-tracks: min-content'' would each result in, and use those sizes.

Subgrids

[=Subgridding=] allows nested [=masonry containers=] (and [=grid containers=]) to share track sizes. If the parent's corresponding axis is a [=grid axis=], the subgridded axis is taken from the parent container [[css-grid-2#subgrids|as specified for grid containers]]; if the parent's corresponding axis is a [=stacking axis=]...
Grid-integrated Syntax: ...the subgridded axis acts like ''masonry''. Note: If this results in ''grid-template/masonry'' in both axes, it is resolved as normal for [=masonry containers=] with double-axis ''grid-template/masonry'' templates, i.e. it acts like ''grid-template-columns: none; grid-template-rows: masonry''.

Grid-independent Syntax: ...the subgridded axis acts like ''grid-template/none''. In [=masonry layout=], auto-placed [=subgrids=] don't inherit any line names from their parent grid, because that would make the placement of the item dependent on layout results; but the subgrid's tracks are still aligned to the parent's tracks as usual.

Here's a subgrid example: ```css ``` ```html
1 2 3 subgrid.1 sub.2 s.3 4 5 6 7
```
The rendering of the subgrid example above.
Note how the subgrid's first item ("subgrid.1") contributes to the intrinsic size of the 2nd row in the parent grid. This is possible since the subgrid specified a definite position so we know which tracks it will occupy. Note also that trying to subgrid the parent's [=stacking axis=] results in the subgrid getting [=masonry layout=] in its [=inline axis=].
A [=subgrid=] that is a [=masonry container=] can be referred to as a submasonry.

Track Repetition: the ''repeat()'' notation

This specification introduces new keywords and masonry-specific behavior for the ''repeat()'' notation.

repeat(auto-areas)

The new auto-areas value for the ''repeat()'' notation represents the number of repetitions necessary for the total number of explicit tracks to match the 'grid-template-areas' / 'masonry-template-areas' value in effect in the corresponding axis. If multiple tracks are listed for the repetition, the final repetition is truncated as necessary to produce the correct number of tracks. Note: Unlike ''repeat()/auto-fit''-- which always repeats at least once and always repeats the track listing entirely-- the number of repetitions for ''repeat()/auto-areas'' can be zero (if there are already enough explicit tracks), and the final repetition can be partial. If 'grid-template-areas' / 'masonry-template-areas' is ''grid-template-areas/none'', this value behaves as ''auto-fit''. Note: This value applies both to regular [=grid containers=] and to [=masonry containers=]. ISSUE(10854): It's unclear if we actually need this value. Note that the explicit grid already takes values from 'grid-auto-columns'/'grid-auto-rows'/'masonry-auto-tracks' as needed to match the number of template areas.

repeat(auto-fit)

In [=masonry containers=] (as in regular [=grid containers=]) ''repeat()/auto-fit'' acts like ''repeat()/auto-fill'', but with empty tracks [=collapsed tracks|collapsed=]. However, because placement occurs after track sizing, [=masonry containers=] use a heuristic to determine if a track will be occupied: * All tracks occupied by explicitly placed items are considered occupied. * With the sum of the spans of all auto-placed items as N, all unoccupied tracks up to the Nth such track are considered occupied. All tracks produced by the ''repeat()/auto-fit'' repetition and considered unoccupied by this heuristic are assumed “empty” and are [=collapsed tracks|collapsed=]. A [=collapsed track=] cannot accept placement of auto-placed items. Note: It is possible for an auto-placed item to be placed in a track when ''repeat()/auto-fill'' is used that would be collapsed if ''repeat()/auto-fit'' is used if there are auto-placed items with a span greater than 1 mixed with explicitly-placed items that leave gaps too small for the auto-placed items.

Grid Axis Track Sizing

Track sizing works the same as in [[css-grid-2#algo-track-sizing|CSS Grid]], except that when considering which items contribute to intrinsic sizes: * All items explicitly placed in that track contribute, and * All items with an [=automatic grid position=] contribute (regardless of whether they are ultimately placed in that track).
For example, suppose there are two columns in the [=grid axis=] and that * Items A, B, and C have no explicit position. * Item D is explicitly placed into the first column. In this case, items A, B, C, and D all contribute to sizing the first column, while only A, B, and C (and not D) contribute to the second column.
In the case of spanning items with an [=automatic grid position=], they are assumed to be placed at every possible start position, and contribute accordingly.
For example, suppose there are 5 columns in the [=grid axis=], with the middle having a fixed size of ''100px'' and the other two being ''grid-template/auto''-sized. For the purpose of track sizing, an item that spans 2 tracks and has an intrinsic contribution of 220px is essentially copied and assumed to exist: * At grid line 1, contributing 110px to each of the first two tracks. * At grid line 2, contributing 120px to the second track. * At grid line 3, contributing 120px to the fourth track. * At grid line 4, contributing 110px to the fourth and fifth tracks.
Note: This algorithm ensures that each track is at least big enough to accommodate every item that is ultimately placed in it, and does not create dependency cycles between placement and track sizing. However, depending on the variation in sizes, tracks could be larger than necessary: an exact fit is only guaranteed if all items are explicitly placed in the [=grid axis=] or all items are the same size (or matching multiples of that size, in the case of spanning items).

Subgrid Item Contributions

When sizing the tracks of either a regular [=grid container=] or a [=masonry container=], a [=submasonry=] has special handling of items that have an [=automatic grid position=]: * Any such item is placed into every possible grid track that could be spanned by the [=submasonry=]. (If the submasonry has a [=definite grid position=], thus only the spanned tracks; if it has an [=automatic grid position=], then all tracks in the parent grid.) * Any such item receives the largest margin/border/padding contribution of each edge at which it could hypothetically be placed. If the item spans the entire subgrid, it receives both. (See CSS Grid Layout §9.)

Optimized Track Sizing

Track sizing can be optimized by aggregating items that have the same span size and placement into a single virtual item as follows:
  1. Separate all the [=masonry items=] into item groups, according to the following properties: * the span of the item * the placement of the item, i.e. which tracks it is allowed to be placed in * the item's [=baseline-sharing group=] Note: For example, an item with span 2 placed in the second track will be in a different group than an item with span 2 that has an [=automatic grid position=].
  2. For each [=item group=], synthesize a virtual masonry item that has the maximum of every intrinsic size contribution among the items in that group. If the items apply [=baseline alignment=], determine the baselines of the [=virtual masonry item=] by placing all of its items into a single hypothetical grid track and finding their shared baseline(s) and shims. Increase the group's intrinsic size contributions accordingly.
  3. Place hypothetical copies of each [=virtual masonry item=] into the [=grid axis=] tracks in every position that the item could potentially occupy, and run the [[css-grid-2#algo-track-sizing|track sizing algorithm]] with those items. The resulting track sizes are the [=masonry container's=] track sizes.
Note: This optimization should give the same results as the track sizing description [[#track-sizing|above]]; if not this is an error, please report it to the CSSWG.

Masonry Placement

In the [=grid axis=], items can be explicitly placed into tracks and span them using the familiar [=grid-placement properties=]’ syntax. Auto-placement, however, uses the [[#masonry-layout-algorithm]], placing each item with an [=automatic grid position=] into the “shortest” masonry track available.
Here's a masonry layout example demonstrating placed and spanning items:
Rendering of the example above.
ISSUE: Need a better example!!!

Grid-integrated Option: Specifying Masonry Item Placement: the 'grid-column-*' and 'grid-row-*' properties

The 'grid-column-*' and 'grid-row-*' properties (and their shorthands) apply in the [=grid axis=] of the items and establish placement just as in regular [=grid layout=].

Grid-independent Option: Specifying Masonry Item Placement: the 'masonry-track-*' properties

Item placement in the [=grid axis=] of a [=masonry container=] is established with the masonry-track-start and masonry-track-end properties (and their masonry-track shorthand), whose syntax and interpretation are analogous to the 'grid-column-start' and 'grid-column-end' properties (and their 'grid-column' shorthand).

Placement Precision: the 'masonry-slack' property

	Name: masonry-slack
	Value: <> | infinite
	Initial: 1em
	Percentages: relative to the [=grid-axis=] [=content box=] size of the [=masonry container=]
	Inherited: no
	Applies to: [=masonry containers=]
	Computed value: a computed <> value
	Animation type: as length
	
[=Masonry containers=] are filled by placing each [=masonry item=] in whichever [=masonry track=] is currently the least filled. When multiple tracks are tied for least-filled, placing the items in order looks good. But if tracks are only very slightly different heights, it can look strange to have them not fill in order, as the height differences aren't perceived as meaningfully different. The 'masonry-slack' property specifies what the threshold is for considering tracks to be “the same height”, causing them to fill in order.
: <> :: Specifies the tie threshold for the [=masonry container=]. Placement positions are considered to be equally good (“tied”) if they are within the specified distance from the shortest position. Note: The initial value is a “small” distance (''1em'') that is probably appropriate to represent “close enough”. : infinite :: Specifies an infinite [=tie threshold=]. This makes items distribute themselves strictly in order, without considering the length of the tracks at all. Note: This value can result in consecutive items being placed in dramatically different positions in the [=stacking axis=], which can be confusing to readers. If the initial value (`1em`) is too small, consider a larger value (such as `10em` or `50vh`) instead of `infinite`.
Issue: Is ''1em'' the right default?

Masonry Layout and Placement Algorithm

For each of the tracks in the [=grid axis=], keep a running position initialized to zero. Maintain also a auto-placement cursor, initially pointing to the first line. For each item in [=order-modified document order=]:
  1. If the item has a [=definite grid position=] in the [=grid axis=], use that placement. ISSUE: Should this also update the placement cursor? Otherwise, resolve its [=grid axis=] placement using these substeps:
    1. Starting at the first [=grid axis=] line in the [=implicit grid=], find the largest [=running position=] of the [=grid axis=] tracks that the item would span if it were placed at this line, and call this position max_pos.
    2. Repeat the previous step for each successive line number until the item would no longer fit inside the grid.
    3. Let |possible lines| be the line that resulted in the smallest max_pos, and all lines that result in a max_pos within the [=tie threshold=] of this max_pos.
    4. Choose the first line in |possible lines| greater than or equal to the [=auto-placement cursor=] as the item's position in the [=grid axis=]; or if there are none such, choose the first one.
    5. Update the [=auto-placement cursor=] to point to item's last line.
  2. Place the item in its [=grid axis=] tracks at the maximum of the [=running position=]s of the tracks it spans.
  3. Calculate the size of the item's containing block and then layout the item. Set the [=running position=] of the spanned [=grid axis=] tracks to max_pos + [=outer size=] + 'grid-gap'.
Note: This algorithm chooses the track that would result in the item being placed as highly as possible. If there are ties, it chooses the earliest such track, after the most recently placed item if possible (ensuring that it always “moves forward” even in the presence of ties). If placing items in reverse order (see 'grid-auto-flow'/'masonry-flow'), the algorithm is analogous but in reverse order.

Containing Block

The [=containing block=] for a [=grid item=] participating in [=masonry layout=] is formed by its [=grid area=] in the [=grid axis=] and the [=grid container=]'s [=content box=] in the [=stacking axis=].

Placement and Writing Modes

Note: Like all of [=grid layout=], masonry layout and placement is sensitive to the [=writing mode=]. For example, for ''direction: rtl'', items are placed right-to-left rather than left-to-right, whether the inline axis is a [=grid axis=] or a [=stacking axis=].
Here's a simple example using ''direction: rtl'' in the [=grid axis=]: ```css ``` ```html
1 2 3 4
```
Rendering of the ''direction: rtl'' example above.
Here's a simple example using ''direction: rtl'' in the [=stacking axis=]: ```css ``` ```html
1 2 3 4
```
Rendering of the ''direction: rtl'' example above.

Sizing Grid Containers

[[css-grid-2#intrinsic-sizes|Sizing Grid Containers]] works the same as for regular [=grid containers=] but with the following addendum for the [=stacking axis=]: The max-content size (min-content size) of a [=grid container=] in the [=stacking axis=] is the size of the [=masonry box=] in that axis when sized under a max-content constraint (min-content constraint).
Here's a simple example: ```css ``` ```html
1 2 3 4 5 6
```
Rendering of the [=grid container=] intrinsic sizing example above.

Alignment and Spacing

[[css-grid-2#gutters|Gutters]] are supported in both axes. In the [=stacking axis=], the gap is applied between the margin boxes of each pair of adjacent items. Margins do not collapse in either axis. In the [=grid axis=], [[css-grid-2#alignment|alignment]] works the same as in a regular [=grid container=]. In the [=stacking axis=], [[css-align-3#content-distribution|content-distribution]] is applied to the content as a whole, similarly to how it behaves in block containers. More specifically, the alignment subject is the masonry box, which is the smallest rectangle bounding the [=margin boxes=] of all the [=grid items=].
The extent of the [=masonry box=] is indicated by the dashed border. (Note that item 1 has a 5px bottom margin here.)
Note: There is only ever one alignment subject for these properties in the [=stacking axis=], so the unique 'align-content' / 'justify-content' values boil down to ''align-content/start'', ''align-content/center'', ''align-content/end'', and [=baseline alignment=]. (The behavior of ''align-content/normal'' and ''align-content/stretch'' is identical to ''align-content/start'', and the [=distributed alignment=] values behave as their [=fallback alignments=].) If the [=grid items=] overflow the [=grid container=]'s [=content box=] in the [=stacking axis=], then the [=masonry box=] will be larger than the [=grid container=]'s [=content box=]. ISSUE: Should alignment in the stacking axis do something more sophisticated? What should that be?

Baseline Alignment in the stacking axis

Item [=baseline alignment=] inside the [=grid axis=] tracks works as usual for a regular [=grid container=], and the [=grid container=]'s baseline is determined the same as for a regular [=grid container=] in that axis. [=Baseline alignment=] is not supported in the [=stacking axis=]. The first baseline set of the [=grid container=] in this axis is generated from the [=alignment baseline=] of the first [=grid item=] in the first occupied track, and the last baseline set from the last [=grid item=] placed. ISSUE: We could support baseline alignment in the first row. Do we want to? ISSUE: Should the last baseline come from the last lowest item placed instead?

Fragmentation

Fragmentation in the stacking axis

Each [=grid axis=] track is fragmented independently in the [=stacking axis=]. If a [=grid item=] is fragmented, or has a [=forced break=] before/after it, then the [=running position=] for the tracks that it spans in the [=grid axis=] are set to the size of the [=fragmentainer=] so that no further items will be placed in those tracks. An item that is split into multiple fragments retains its placement in the [=grid axis=] for all its fragments. A grid item that is pushed, however, is placed again by the next [=grid container=] fragment. Placement continues until all items are placed or pushed to a new fragment.
Here's an example illustrating fragmentation of a grid with masonry layout in its [=block axis=]. It renders like this:
Visualization of fragmentation in a [=block-axis=] [=masonry layout=].

Fragmentation in the Grid Axis

Fragmentation in the [=grid axis=] with [=masonry layout=] in the other axis is also supported. In this case the fragmentation behaves more like in a regular [=grid container=]; however, there's a separate step to determine which [=grid-axis=] track each item is placed into, before fragmentation occurs.
Here's an example illustrating fragmentation of a grid with [=masonry layout=] in its [=inline axis=]. In this case the breaks occurs between the [=grid-axis=] rows. It renders like this:
Visualization of fragmentation in the [=block axis=] with [=inline-axis=] [=masonry layout=].

Absolute Positioning

[[css-grid-1#abspos-items|Grid-aligned absolute-positioned descendants]] are supported in [=masonry containers=] just as for regular [=grid containers=]; however, in the [=stacking axis=] there exist only two lines (in addition to the ''grid-area/auto'' lines) for placement: * line 1 (line -2) corresponds to the start edge of the [=masonry box=] * line 2 (line -1) corresponds to the end edge of the [=masonry box=] ISSUE: It might be useful to define a static position in the [=stacking axis=]. Maybe it could defined as the max (or min?) current [=running position=] of the [=grid-axis=] tracks at that point? Or the end of the item before it?

Graceful Degradation

Typically, a masonry design can be expected to degrade quite nicely in a UA that supports Grid layout but not masonry layout if the 'grid'/'grid-template' shorthands are avoided and the longhands are used instead. e.g. ```css grid-template-rows: masonry; /* ignored by UAs that don't support it */ grid-template-columns: 150px 100px 50px; ```
Here's an example to illustrate this. It's a layout with three columns, but will have "more gaps" in the [=block axis=] if the UA doesn't support masonry layout. Here's what it looks like with Masonry support for comparison:
Rendering of the example in a UA with Masonry support.

Acknowledgements

Thanks goes to Cameron McCormack who wrote a masonry layout explainer document (from which was lifted the Background chapter) and presented it to the CSSWG, and to Mats Palmgren who developed the original version of this specification. Thanks also to everyone who provided feedback on the initial proposal for this feature.

Security Considerations

As a layout specification, this spec introduces no new security considerations beyond that exposed by CSS layout in general.

Privacy Considerations

As a layout specification, this spec introduces no new privacy considerations beyond that exposed by CSS layout in general.

Changes

Additions Since Level 2

The following features have been added since Level 2:

Recent Changes

The following changes have been made since the First Public Working Draft: * Drafted ability to mix ''auto-fill''/''auto-fit'' ''repeat()'' values with content-based track sizes in the [=grid-independent option=] and made it the initial behavior 'masonry-template-tracks'. (Issues 10915, and 10869) * Added ''masonry-slack: infinite''. (Issue 10883) * Minor corrections, updated acknowledgements, and added an example.