- From: rjgotten via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Sep 2024 11:58:36 +0000
- To: public-css-archive@w3.org
> ### Benefits of Treating the Masonry Layout as Part of the Grid Layout > > One of the key benefits of integrating masonry into the grid layout (as in CASE 2) is the ability to leverage existing grid features, such as subgrids. Subgrids allow for cohesive designs among child elements within a grid, something highly desirable in many masonry layouts as well. This is a false dichotomy and should be dismissed as a benefit on that alone. The syntax and semantics of the CSS that will drive masonry layout is a concern that is separate from the actual layout mechanics itself, which internally in implementation by user agents can still re-use parts of the existing mechanics for grids, including subgrids. For cases where masonry is nested inside grid, or grid inside masonry, the relationship between the two can be made explicit. And a syntax separate from the grid syntax can still incorporate a `subgrid` keyword to establish the parent-child relationship. Albeit, maybe that should be generalized to just be `sub`, where `subgrid` becomes an alias to `sub`. -- GitHub Notification of comment by rjgotten Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2363560261 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 September 2024 11:58:37 UTC