- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2025 13:14:54 +0000
- To: public-css-archive@w3.org
I think one concern I have with having a separate value for the block size, is that we then end up with situations such as an author wanting overflow in the block direction, setting a height on the multicol, and the row height however there still isn't enough space in the multicol container for all of the rows (due to the height). What happens then? The dev ergonomics currently are: 1. Set a height. 2. Get overflow columns in the inline direction The future spec (my version) 1. Set a height 2. Choose whether to get overflow columns in the inline or block direction, by setting them to wrap. Multicol is a pretty simple thing, in terms of how it's used. I get that having a separate size for rows might open up a bunch of other possibilities, but are they possibilities that anyone actually needs for multicol? Or are we just making the spec more complex because it might be nice to do that stuff at some point. That said, I'm not completely against the idea, and we should discuss it, I'm just wary of making something complex for the sake of it. We have more complex layout methods, we could potentially introduce something more like regions to do the more complex fragmented cases ... I'm thinking we probably don't want to morph multicol into something that does bits of regions-like things, but never really fulfils that idea. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2923#issuecomment-2624487481 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 January 2025 13:14:55 UTC