- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Apr 2024 18:56:04 +0000
- To: public-css-archive@w3.org
I talked about this on the call, but when I first starting showing people flexbox and grid, a very frequent comment was that they behaved inconsistently. What they meant was that they behaved differently to their assumptions about how things behave in block layout. At this point, I think we've been able to get a reasonable understanding of what it means to change formatting content across to developers. For example, to understand why certain alignment properties don't apply in flexbox. If we bundle masonry with grid, I fear we end up with a situation where we have to say "these properties/values work in a grid formatting context but not if you are using masonry" or "these only work if you are in a grid formatting context AND using masonry". That's not just things that exist today (such as the alignment properties), but anything we might want to add in the future. As Tab mentioned above, we can reuse a lot of grid things in `display: masonry`, we don't lose all the things Jen has shown in her demos because we define it as a new spec, but we also don't end up dancing around the differences forever. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9041#issuecomment-2075620726 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 April 2024 18:56:05 UTC