- From: ecbypi via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Oct 2024 13:24:00 +0000
- To: public-css-archive@w3.org
My 2 cents: integrating masonry into `display: grid` seems like a safer approach that's less disruptive to people browsing the web. Overall, I'm "meh, why?" on incorporating masonry into the browser as I don't find it a friendly experience for people that have issues with focus or cognitive challenges. It's a perennial issue getting people to be aware of and care about inclusivity in design and engineering; using `display: grid` seems like a safer, more conservative approach to start. From what I can see, the `display: grid` approach doesn't seem to preclude implementing `display: masonry` in the future after learning how people use it as part of `display: grid` (for better or for worse) and seeing what limitations need to be addressed. Other thoughts: * For me, the points about "masonry's future" are missing meaningful, genuinely useful, accessible examples that demonstrate why `display: masonry` is required, how it would simplify the implementation in browsers, or be easier for developers to use than an implementation using `display: grid`. * Instead of optimizing for assumptions about developer convenience, I'd rather optimize for customer experience and `display: grid` would result in fewer broken interfaces. Eventual evergreen support in all browsers is an assumption and ignores people depending on unsupported devices. * It's convenient when the model to teach a technology is simple, but the absence of that doesn't make the technology unteachable. * To share my own assumption to counter other assumptions: simplicity for teaching or usage could be offset by confusion from similarities between `display: grid` and `display: masonry`. Naming the properties differently does not unequivocally prevent people from making false assumptions about similarities between them. -- GitHub Notification of comment by ecbypi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11060#issuecomment-2437772454 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 25 October 2024 13:24:01 UTC