W3C home > Mailing lists > Public > www-style@w3.org > December 2007

RE: [css3-multicol] Column Breaks

From: Alex Mogilevsky <alexmog@exchange.microsoft.com>
Date: Wed, 12 Dec 2007 09:21:38 -0800
To: "www-style@w3.org" <www-style@w3.org>, fantasai <fantasai.lists@inkedblade.net>
Message-ID: <04F36FB4ED0F85459AA447F72711526F011F3F0FD43B@DF-GRTDANE-MSG.exchange.corp.microsoft.com>

I agree. I would be much easier to both understand and implement if there was only one set of properties controlling breaks. And column-break that is a page-break at the same time is a case that is solvable but definitely not intuitive.

There is only one column-break property that is not included in page-breaks:


what if instead we use


That would cover all use cases, wouldn't it?

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of fantasai
Sent: Tuesday, December 11, 2007 4:21 PM
To: WWW Style
Subject: [css3-multicol] Column Breaks


I'm not quite convinced that we need separate properties for
column breaking. If the use case is forcing a column break, then
I think adding keywords to page-break-before and page-break-after
should be sufficient. If the use case is offering a different
level of breaking restrictions for columns than for pages, then
we also should have column-break-inside, column-windows, and

I do think that if we have separate properties, the default value
should be defined such that it references the page-break-*
properties. That way, unless I really want separate sets of rules
for the two types of breaks, I only have to set the breaking
behavior once. This is particularly important when using the
'avoid' values.

What happens when there's a column break that's also a page break?
Do we use the page-break properties to control breaking behavior
or the column-break properties, or some combination thereof?

Received on Wednesday, 12 December 2007 17:21:59 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:13:24 UTC