- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 20 Aug 2025 11:30:37 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-multicol-2] Should multicol wrapping happen in paged media and nested multicols?`, and agreed to the following: * `RESOLVED: column-height does apply in nested contexts` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> rachelandrew: when i proposed block-direction:overflow, i'd only ever thought about continuous contexts (web), not paged media<br> <TabAtkins> rachelandrew: as i discussed with morten, he wondered if that's what we wanted. also brought up complexity around nested multicol<br> <astearns> zakim, open queue<br> <Zakim> ok, astearns, the speaker queue is open<br> <astearns> q+ fantasai<br> <TabAtkins> rachelandrew: i don't see any particular reason to do this in paged media. lots of complexity when you already have a fixed-size thing<br> <TabAtkins> rachelandrew: if it's only for continuous context, then, we could also say it doesn't happen in a nested multicol context. morten agree with this<br> <TabAtkins> rachelandrew: i've never seen an example of nested multi-row multicol in the wild<br> <astearns> q+<br> <TabAtkins> rachelandrew: so that's my proposal<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: I disagree with doing this.<br> <TabAtkins> fantasai: I think we shoudln't transform the layout so substantially when printing<br> <TabAtkins> fantasai: also sometimes people use nested multicol to simulat epagination<br> <TabAtkins> fantasai: that said, fragmenting these rows doesn't make sense. we def shouldn't do that<br> <TabAtkins> fantasai: i think the right thing is to say that...<br> <TabAtkins> fantasai: ahven't thought this thru yet<br> <TabAtkins> fantasai: we dont' want to break inside a column row, just between<br> <TabAtkins> fantasai: so q is how tall are the columns - do we shorten them near the bottom of the page, or push them to the next page?<br> <TabAtkins> rachelandrew: that's the next issue<br> <TabAtkins> fantasai: so if block-direction wrapping does happen in nested fragmentation, you just never fragment a row of columns<br> <kizu> +1<br> <TabAtkins> rachelandrew: that does simplify things a bit. we'll have to decide what to do with th eleftover space, i think there's an issue for that<br> <astearns> ack astearns<br> <TabAtkins> astearns: we did consider this when we were going thru Regions<br> <TabAtkins> astearns: so there are bit in Regions about nested fragmentation contexts, and in the Fragmentation module about nested flows<br> <TabAtkins> astearns: don't recall our use-cses. but there's something there to build on.<br> <TabAtkins> astearns: but generally i agree with elika, there are layouts with reason to have multiple rows to be displayed on each page.<br> <TabAtkins> astearns: not working when nested will break some people's sites<br> <TabAtkins> rachelandrew: okay, that's about it for this topic then<br> <TabAtkins> astearns: should we take a resolution that column-height does apply in paged media?<br> <TabAtkins> rachelandrew: in nested contexts in general<br> <TabAtkins> astearns: so proposed resolution is that column-height does apply in nested contexts<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: column-height does apply in nested contexts<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12593#issuecomment-3205806899 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 August 2025 11:30:37 UTC