- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 May 2024 17:12:59 +0000
- To: public-css-archive@w3.org
Oh, huh. *Only* aligning the last one seems fairly odd to me. Jen's examples look good and the use-cases are definitely reasonable, but all the images have only *one* element being affected, so it doesn't demonstrate the difference in question. If there were multiple elements, especially if there were 3+, I think it would look odd if all it did was change it from "the entire stack of elements is start-aligned" to "the entire stack of elements is start-aligned except for the last one, which is end-aligned". This seems extra true for `center`. (`stretch` might look okay, tho.) > I agree that aligning the entire stack could be useful, too, but it runs into the problems @bfgeek outlined for https://github.com/w3c/csswg-drafts/issues/8207 which is why that feature was removed. No, in that issue @bfgeek was objecting to the ability to align the contents of each track *independently* - giving one track start alignment, another end alignment, etc. He recognized the value in being able to align *all* the tracks in a given direction: "The use-cases I've seen here typically align masonry axis tracks together rather than individually." and the following paragraphs in his comment. Non-start alignments *applied to the whole masonry* can somewhat misalign the reading order from the dom order, but generally not to an enormous degree (and generally no more than what `masonry-threshold` can do). -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10275#issuecomment-2101040402 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 May 2024 17:13:00 UTC