- From: Mustafa Enes Ertarhanaci via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Apr 2024 01:47:27 +0000
- To: public-css-archive@w3.org
Hi all, while reading the article, I thought about the possibility of having the masonry as a new `display` value that can sufficiently interoperate with grid properties, like the flex currently does (e.g. `gap`, `justify-*` / `align-*`). This would (perhaps) simplify the browser implementations and (perhaps) the mental modelling for developers and designers, since it will not automatically force every grid feature to (possibly incorrectly) work with the proposed masonry rows. Instead, the masonry could grow its own vocabulary free of every other grid feature. On the other side, the new display type would _just work™_ with the most relevant parts of the grid layout (e.g. fine control over columns, gap). I personally have no strong preference/opinions on either way. Masonry in any form would be a leap forward. Also, I think the spec should warn us of possible accessibility pitfalls, like: > Maybe I missed it, but is there any 'Responsive' technology being discussed to make these new web features work for people who don't have the huge screen area to take advantage of them? Or for people dependent on Alt text? WAVE shows no Alt text at all in the demo. And if there was, a grid of 51 images would be a bit much to navigate... > > In that vein, WAVE finds no headings! "Headings ... provide important document structure, outlines, and navigation functionality to assistive technology users." There really needs to be some rational structure within the page for those of us who can't just glance at the whole wall of images at once! *** Thanks! 💛 -- GitHub Notification of comment by scriptype Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10233#issuecomment-2071260513 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 April 2024 01:47:28 UTC