W3C home > Mailing lists > Public > www-style@w3.org > January 2008

RE: [CSS2.1] [CSS3-Page] allowed breaks and fixed heights

From: Alex Mogilevsky <alexmog@exchange.microsoft.com>
Date: Thu, 17 Jan 2008 23:17:12 -0800
To: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <04F36FB4ED0F85459AA447F72711526F012543DF0152@DF-GRTDANE-MSG.exchange.corp.microsoft.com>

I agree it makes much more sense to break within padding than to move content to a different page when padding doesn't fit.

My first reaction was that if padding and border don't fit, they should be clipped and not even appear on the next page. However as I thought about it, if a page is designed primarily for screen, it makes sense to paginate content-free parts, just to preserve overall shape of the page...

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of fantasai
Sent: Thursday, January 17, 2008 10:08 PM
To: www-style@w3.org
Subject: Re: [CSS2.1] [CSS3-Page] allowed breaks and fixed heights

fantasai wrote:
> However I think we should allow breaks between the line box and the content edge if
> there is extra space in between. I believe this is what most browsers do, and I suspect
> many float-based layouts especially would break when printed if we did not allow this.
> If the author really wants the block to stay together, he can set page-break-inside:
> avoid.
> I'll post testcases in a bit..


UAs that break between the bottom of the last line box and the bottom content edge:
   - IE7
   - Firefox
   - Safari (Windows)
   - Konqueror
   - Prince (Prince truncates the bottom of the box.)

Opera is the only browser I tested that pushes the last lines to the next page in
order to not break between the last line box and the content edge. I'm not convinced
it's an improvement in the printed result.

Received on Friday, 18 January 2008 07:17:40 UTC

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