- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Dec 2022 20:12:17 +0000
- To: public-css-archive@w3.org
bfgeek has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-grid-3] Masonry - align-tracks / justify-tracks potentially not desirable for accessibility. == This feature of css-grid-3 allows developers to align tracks individually. However this creates a disconnect pretty quickly with the "visual order" and the "box order" of the document. Example 9 in the spec demonstrates this well: https://drafts.csswg.org/css-grid-3/#masonry-axis-alignment The tab order for above would be 1,2,3,4... etc. However the visual order for that example definitely not that :). The use-cases I've seen here typically align masonry axis tracks together rather than individually. Something to lean on here might be something similar to how flexbox works in that you can start the masonry algorithm for the "end" side, instead of the "start" (e.g. row-reverse and friends). Note this problem is different to alignment on individual grid/flex items, as for those layout modes alignment happens within a line/track, and the visual order still matches the box order. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8207 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 December 2022 20:12:19 UTC