[css-grid-3][masonry] Masonry Syntax Debate

[fantasai]

The CSSWG's masonry layout draft includes two competing syntax proposals for the feature. There has been a lot of discussion between the two, and there's an overview of the debate in the TAG review issue.

Opening this issue to focus on the syntax question, since the previous issue debating two possible models started with focus on the performance implications of mixed track sizing, etc. that are no longer relevant.

Key links (primary in bold):

• TAG Review Request: Overview of the syntax debate
• Chrome Blog: How should we define CSS masonry?
• WebKit Blog: Help us choose the final syntax for Masonry in CSS
• Ahmad Shadeed: Should masonry be part of grid?
• Rachel Andrew: Masonry and good defaults
• Keith J. Grant: Weighing in on CSS masonry [published before the merged FPWD]
• Chrome Blog Comments Chrome directed developers to tack their comments onto the end of the "Alternative Masonry Path" issue, which had been opened to debate a number of things including syntax...
• WebKit Blog Comments WebKit opened this fresh issue for syntax-focused comments after the latest developments, closing out an older issue from an earlier blog post collecting more general feedback on masonry layout capabilities...

[astearns]

A couple of questions for folks to (maybe?) spark some discussion:

• What is the strongest argument for the option you do not prefer?
• If you have changed your opinion from one of the options to the other, what was the reason for the change?

[astearns]

TAG feedback: w3ctag/design-reviews#1003 (comment)