- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Dec 2024 08:57:12 +0000
- To: public-css-archive@w3.org
By automatically, I'm assuming that the default behavior of `grid-auto-flow: dense` and masonry layout or using would be to follow the 'visual' order, rather than source order. Given that masonry is new, there wouldn't be an issue there as we could define the behavior from the outset. I outlined some thoughts for the masonry/reading-flow interactions in [this issue](https://github.com/w3c/csswg-drafts/issues/5675#issuecomment-2565155995). Having automatic behavior would I think mean we needed to have the behavior more like flex, and have a `masonry-flow` value as the behavior of `normal` in masonry layouts. Changing the defaults for dense packing might cause a compat issue. My gut feeling tells me that where people have used dense packing they aren't too worried about the ordering, given that you essentially lose control of it anyway, but we probably need to look into it. The default would likely need to follow the `grid-auto-flow` direction (so `reading-flow: grid-rows` for `grid-auto-flow: row dense`). I think in both cases adding a keyword to `reading-flow` (perhaps `source`) to reset it would be needed. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11396#issuecomment-2565198529 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 December 2024 08:57:13 UTC