- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Oct 2024 22:30:49 +0000
- To: public-css-archive@w3.org
Any two-dimensional value doesn't make sense in Masonry; it needs to be either re-interpreted as 1d or (perhaps partially) ignored. * `grid-row` (when you have a column masonry), and the corresponding `grid-row-start` and `grid-row-end` properties * `grid-area` using the 4-value syntax * `grid-template-areas` defining more than one row and column * `grid-auto-rows` (when you have a column masonry) * `grid-auto-flow` *all* currently values are useless (Masonry *always* auto-flows and doesn't do `dense`). The `*-reverse` keywords introduced in Grid 3 do make sense in Masonry, but one of them is useless depending on whether you have a row or column masonry. (And, as currently defined, the one that actually works is *confusing*: a column masonry uses `row-reverse` to break column ties from right to left, because a **Grid** would use `row-reverse` to indicate that its *rows* are filled from the right to left. But a column masonry doesn't *have* rows, it just fills its columns in a directly *reminiscent* of a Grid filling its rows.) * 'align-self' and 'align-items' (on a column masonry) do nothing (and that's correct and fine; they do nothing in `display:masonry` too) As for Masonry-only: * `masonry-slack` determines when there are ties in masonry placement; it does nothing in Grid * using intrinsic size keywords in auto-repetitions when defining tracks (`repeat(auto-fit, auto)`) only works in Masonry -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2394749289 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 October 2024 22:30:50 UTC