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

RE: [css3-gcpm] Multi-column floats overflowing the column

From: Alex Mogilevsky <alexmog@exchange.microsoft.com>
Date: Sun, 6 May 2007 13:56:55 -0700
To: Håkon Wium Lie <howcome@opera.com>, "del@alum.mit.edu" <del@alum.mit.edu>
CC: Brady Duga <duga@ljug.com>, W3C CSS <www-style@w3.org>
Message-ID: <04F36FB4ED0F85459AA447F72711526FD62FE94EFD@DF-GRTDANE-MSG.exchange.corp.microsoft.com>

I agree, it makes sense to have widows/orphans behave the same way on column breaks as on page breaks.

Note that since on multicolumn page a page break is also a column break, these settings control breaking behavior across both column and page boundaries.

If we wanted to control this at column level independently we'd need separate properties, which I hope we can avoid (although I don't have strong feelings about it).

-----Original Message-----
From: Håkon Wium Lie [mailto:howcome@opera.com]
Sent: Sunday, May 06, 2007 7:32 AM
To: del@alum.mit.edu
Cc: Brady Duga; Alex Mogilevsky; W3C CSS
Subject: Re: [css3-gcpm] Multi-column floats overflowing the column

The newer draft doesn't say anything about 'widows' and 'orphans',
perhaps it should. The definition of the 'widows' and 'orhpans'
properties only refers to pages, not columns. It seems reasonable that
'widows' and 'orphans' also apply to columns so that one could write:

  div.section {
    columns: 2
    widows: 3;
    orphans: 3;
Received on Sunday, 6 May 2007 20:57:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:28 UTC