- From: Naman Goel via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Oct 2024 03:25:27 +0000
- To: public-css-archive@w3.org
@tabatkins First, let me defend Nicole's talk. It wasn't biased in the same way the webkit blog post was. It didn't favour either API proposal and intentional tried to stray away from the topic entirely. It mostly presented the cool stuff that might be coming to CSS and asked for feedback. She also presented a few pieces of feedback she had received from various devs. None of these pieces of feedback moved me in favour of either proposal. They were generally ideas about things that *neither* API support as written today. And so I just came to add to that conversation, not take part in this heated debate about which API anymore. It's not important enough to me. Even if the proposal I like less gets standardised, I will still be happy about it. And so... - In my last comment I didn't express any opinion on which API should be chosen. - I asked for the ability to have `grid-row: span fit-content` for grid layout. This is not relevant to the masonry proposal, but I mentioned it here, because I think it's loosely related. - I do think a "packed" layout with no "tracks" in *either* axis is something that is sometimes desirable. Imagine a word cloud, or an image cloud which creates a collage-like layout. I'm not sure if that belongs in masonry layout, but I figured it's useful to bring it up now in case it is. --- I know this debate has gotten quite heated and maybe even a bit ugly, so I understand your reaction. But despite my earlier comments taking sides in the debate, I've moved on. -- GitHub Notification of comment by nmn Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2387555785 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 October 2024 03:25:28 UTC