Re: [csswg-drafts] [css-grid-2] Masonry layout (#4650)

The main issue I see with rolling this into grid, is as previously mentioned in this thread. If we roll this into grid layout then we have things that authors reasonably expect a grid layout to do which start to behave in perhaps an unexpected way once we roll Masonry into the mix. Folk already have issues when they mix placed items with auto-placement for example, as that behavior isn't always intuitive.

In addition I can see it adding a layer of complexity to anything we might want to add to the grid layout module in future, in terms of how this addition works with Masonry layout, we either say it doesn't (and therefore add confusion for authors) or we have to spend additional time making it work. 

Because of this I much prefer this being it's own thing, or as @argyleink has suggest part of Flexbox, as it is far less likely that features will be added to the flexbox spec, which would make Masonry a burden that needed to be worked around.

I would also note that even in the most trivial of demos you start to get layouts with some degree of separation of the content order and layout, enough that it would cause weird jumps if tabbing around a list of products for example. It was brought up in the CSSWG meeting in Spain where this was discussed that perhaps we should be addressing that disconnect before adding additional layout methods which make it easy for people to cause this problem, and I would tend to agree.

-- 
GitHub Notification of comment by rachelandrew
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4650#issuecomment-623908272 using your GitHub account

Received on Tuesday, 5 May 2020 07:48:23 UTC