The Chrome team is very keen to unblock masonry, we know it's something developers want.
Defining masonry outside of the grid specification does not prevent multiple track sizes for masonry, or the use of properties such as alignment or gaps, or any other features used in grid layout.
The Chrome team believes that masonry should be a separate layout method, defined using display: masonry (or another keyword should a better name be decided upon).
Performance: Grid and masonry are opposite in terms of how the browser deals with sizing and placement, leading to potential layout performance issues.
[
add
]
[
|
|
...
]