- From: Kent C. Dodds via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Nov 2024 16:50:04 +0000
- To: public-css-archive@w3.org
I’ve been following the discussion here, and I think an important guiding principle is to avoid prioritizing short-term issues over long-term maintainability and usability. While baking masonry into the grid spec would indeed help with progressive enhancement, that challenge is temporary. As browser support catches up, the progressive enhancement issue fades, but the learning complexity and configuration burden would remain. Adding `display: masonry` might duplicate some grid features and be harder (not impossible) to progressively enhance, but it would provide a simpler, more intuitive approach for developers, especially those who may only need masonry layouts occasionally. Over time, I think we benefit more from a distinct `display: masonry` property that’s straightforward to learn and configure than from a tightly integrated but complex grid enhancement. -- GitHub Notification of comment by kentcdodds Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11060#issuecomment-2471055680 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 November 2024 16:50:05 UTC