W3C home > Mailing lists > Public > www-style@w3.org > April 2009

Re: [css3-multicol] page-break-inside and columns

From: Philip TAYLOR <P.Taylor@Rhul.Ac.Uk>
Date: Thu, 09 Apr 2009 09:49:06 +0100
Message-ID: <49DDB682.7050208@Rhul.Ac.Uk>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: fantasai <fantasai.lists@inkedblade.net>, Håkon Wium Lie <howcome@opera.com>, www-style@w3.org


Tab Atkins Jr. wrote:

>>> My main concern here is that /usually/, you want to set both
>>> page-break-* and column-break-* to the same thing.
>> I disagree.  Can you say on what basis you arrived at this
>> conclusion, please ?
> 
> I can't answer for Elika, but it seems true to me.  If you want to
> avoid a break in an element, *generally* you want to avoid it
> unilaterally.

Again, this seems to be an over-generalism to me, so once
I again I appeal for information as to the basis on which you
reach your conclusion.  Let me say that I accept the hierarchical
nature of breaking : if I want to avoid column breaks, then
(almost) "of course" I want to avoid page breaks.  But I cannot
accept the converse at all.  If I want to avoid page breaks,
then presumably the reason is to avoid some part of the text
being invisible when looking at another part.  But columns do
not cause invisibility, and hence I see the demand for
inhibiting column breaks as being far rarer than the demand
for inhibiting page breaks.

Incidentally, all of the preceding is in the context of
"avoid-inside", not in the context of "avoid-between",
which is an entirely different kettle of fish.  I do
wonder if whether this contextual difference lies at
the heart of this disagreement : are some (yourself, Fantasai)
thinking primarily in terms of "avoid-between", whereas
I am thinking primarily in terms of "avoid-inside" ?

Philip TAYLOR
Received on Thursday, 9 April 2009 08:49:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:46:58 GMT