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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 7 Apr 2009 13:24:13 -0500
Message-ID: <dd0fbad0904071124j6b1ade68ybc8d736ffe11b0ff@mail.gmail.com>
To: "Philip TAYLOR (Ret'd)" <P.Taylor@rhul.ac.uk>
Cc: Sylvain Galineau <sylvaing@microsoft.com>, CSS <www-style@w3.org>
On Tue, Apr 7, 2009 at 12:57 PM, Philip TAYLOR (Ret'd)
<P.Taylor@rhul.ac.uk> wrote:
> Sylvain Galineau wrote:
>> I think Melinda alluded to it earlier. If you have a picture followed by
>> an explanatory paragraph, it would be highly desirable to keep them together
>> i.e. no page or column break between the picture
>> and the text. Otherwise, you could end up with your figure at the bottom
>> of a column and the related paragraph at the top of the next one e.g.
>> starting with "In the graph above...". Much worse if there is a page break,
>> of course.
>> So I would expect the author to instruct the formatter to attempt to keep
>> them together with no breaks.
> I can see this, but I think that there is an important
> difference between avoiding a break /between/ (say) an
> image and (the start of) some text, and avoiding a
> break /within/ the text.  Hakon explicit said :
>> I think it's a common scenario that authors don't want elements to
>> break. No?
> and I was interpreting this quite strictly : no breaking
> /within/ elements; I think that the scenario you are
> postulating is the avoidance of a break /between/ elements,
> is it not ?

Not quite.  If you have a very simple structure, such as an <img>
always followed by a single <p> for a caption, then yes.  In a more
general sense, though, where you may have a title for the image, and
possibly more than one sibling element referring to it, you'd want to
avoid breaks between *all* of them, which is something very difficult
and error-prone to specify.  Luckily you can semantically pack these
into a <figure> element, at which point you'd like to say that you
want to avoid breaks inside of any and all <figure>s.  This addresses
the issue with little to no chance of errors, no matter what markup
you've chosen to associate with an image.

Received on Tuesday, 7 April 2009 18:24:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:25 UTC