4 ms·

I think one additional point to consider when adding it as a new display mode vs re-using grid, is that currently these demo's fallback quite nicely now when it

I think one additional point to consider when adding it as a new display mode vs re-using grid, is that currently these demo's fallback quite nicely now when it's re-using grid. Instead of showing it as masonry (since my browser doesn't support it), it at least behaves as a grid. If it's a new display: X property, it will fallback to div behavior with the content all over the place in unsupported browsers.

laszlokorte 3y ago
you could simply do: "display: grid; display: masonry;" and all not-supporting browsers would skip the second declaration.
- yurishimo 3y ago
  This is assuming there isn’t any cross pollution of shared properties either.
  - danielheath 3y ago
    `@supports masonry { shared-property: 1; }`