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

Re: [css-break] breaking inside padding

From: Alan Stearns <stearns@adobe.com>
Date: Mon, 16 Dec 2013 21:21:23 +0000
To: François REMY <francois.remy.dev@outlook.com>, 'fantasai' <fantasai.lists@inkedblade.net>
CC: "www-style@w3.org" <www-style@w3.org>, 'Dave Cramer' <Dave.Cramer@hbgusa.com>
Message-ID: <CED4ADEC.350A7%stearns@adobe.com>
On 12/13/13, 12:38 AM, "François REMY" <francois.remy.dev@outlook.com>

>I think we should have two modes for [css3-break]:
>- fragmentainer-overflow: avoid // default on almost everything
>- fragmentainer-overflow: none // default on printed @pages
>When "fragmentainer-overflow: none" is set, it is simply forbidden for an
>element to overflow its fragmentainer. In case the first breaking point
>available would result in an overflow of the content out of the
>fragmentainer, the "bitmap-based" algorithm we currently see in browsers
>except FireFox would apply.
>It seems clear to me that, when printing, the desire is to avoid printing
>off-page which is why browsers fragment according to this pixel-line

I agree that it would be good to have a switch for this behavior, and have
been arguing for something like this to use in scrollable views that can
handle overflow better than printed pages. But I’m happy just defining the
print-based behavior for this level of the fragmentation module and
deciding whether to add a switch like this later.



Received on Monday, 16 December 2013 21:21:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:17 UTC