- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Apr 2024 15:10:32 +0000
- To: public-css-archive@w3.org
> will get you the behavior of 'next' except in cases where the "change in size" isn't actually "small" Consider a threshold of 10px. If we have three columns filled with `100px, 90px, 80px`, then the next item will go into the 2nd column. But if the last item placed in that column becomes 0.1px larger, resulting in columns filled with `100px, 90.1px, 80px`, then we would place the next item into the 3rd column. And from that point on, things can change radically. > If you set it to infinity, it gets you exactly the behavior of `next` That doesn't seem to follow from the definition in #9328: "among all the columns within slack distance of the shortest column, place in the startmost" The 1st column will always be within an infinity distance from the shortest column, so all items will go into the 1st column. I guess the logic could be modified to: 1. Let `x` be the last column that received an item, if any. 2. If there is no `x`, pick the first column and abort these steps. 3. Find the candidate columns within the threshold from the shortest one. 4. Pick the startmost candidate column that comes after `x` and abort these steps, if any. 5. Otherwise, pick the startmost candidate column. I think that would really be the `next` behavior. Then I would be fine with dropping `masonry-auto-flow: next`. But `masonry-threshold: calc(1px / 0)` seems quite hacky, I would prefer to add a keyword for it. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10232#issuecomment-2072636648 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 15:10:33 UTC