Open fantasai opened 1 month ago
Yeah, we lost the definition of how to handle intrinsic track sizes during repetition when we figured out the compromise layout algorithm. I've set down what I think is a reasonable definition (basically just restoring the old behavior from my draft) in https://drafts.csswg.org/css-grid-3/#masonry-intrinsic-repeat, along with an explanation of why the definition is the way it is.
This has been spot-reviewed by @bfgeek, but not yet by the MS engineers actually doing the experimental implementation.
OK, split out the question of whether/how to define auto-repeats into https://github.com/w3c/csswg-drafts/issues/10915 ; leaving this issue to just the question of what the initial value should be (assuming both are possible).
The initial value of
grid-template-columns
isnone
, which ends up creating as many tracks as there are template areas, sizing them pergrid-auto-columns
.Tab's Alternate Masonry Proposal instead uses an initial value of
repeat(auto-areas, auto)
which repeatsauto
to match the template areas (ignoringmasonry-auto-tracks
), and falls back torepeat(auto-fill, auto)
... which is technically not defined atm, since auto depends on explicit placement.What should the initial track listing be for masonry layout?