- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 Apr 2024 18:28:21 +0000
- To: public-css-archive@w3.org
Yeah, you're right, my proposed algo was bad. Masonry naturally displays a desirable "fill start-to-end" behavior when items are all the same size, and a small threshold just puts a little flexibility into that behavior; a large threshold should give it *large* flexibility, rather than drastically changing the behavior to something completely different. I don't really like the behavior of your algo when explicitly-placed items get into the mix, tho. I've been playing around with it a bit, and I think we get the best results if we just don't update the "last placed" cursor for explicit items. I got sniped and wrote up [a live example of the layouts](https://xanthir.com/etc/tests/masonry/algos.html) to play around with. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9328#issuecomment-2079917824 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 26 April 2024 18:28:22 UTC