You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People have been trying to use CSS for <a href="https://github.com/w3c/csswg-drafts/issues/1009#issuecomment-278095001">masonry layouts</a> for over a decade,
381
-
and it doesn't seem to have slowed,
382
-
so it's probably not just a layout fad.
383
-
Would probably be worthwhile to address officially.
384
-
385
-
As far as I can tell,
386
-
this is best done as a Grid feature;
387
-
some of the features I've seen in masonry libraries
388
-
(like large items spanning multiple masonry tracks)
389
-
make Flexbox inappropriate.
390
-
This also would reuse *so many* Grid features
391
-
that it would be a shame to put together a brand new layout spec for it.
392
-
393
-
No clue what it would look like yet, tho.
394
-
In handwavey terms, it's a grid that's only gridded
395
-
"in one dimension",
396
-
and free-flows in the other,
397
-
with auto-flow.
398
-
399
-
Note that this is actually 100% possibly with Grid today,
400
-
if your items are of known height,
401
-
by making thousands of 1px tall rows,
402
-
and setting the items' row-span to be equal to their height in px.
403
-
(Or some lower-res multiple, like 10px rows.)
404
-
Dense row auto-flow then magically makes Masonry happen.
405
-
This is just a terrible hack that runs into memory/CPU issues
0 commit comments