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

Re: [css-break] another fragmentation question

From: Morten Stenshorne <mstensho@opera.com>
Date: Fri, 19 Jul 2013 00:33:14 +0200
To: Fran├žois REMY <francois.remy.dev@outlook.com>
Cc: "www-style\@w3.org" <www-style@w3.org>
Message-ID: <87hafrqz11.fsf@aeneas.oslo.osa>
Fran├žois REMY <francois.remy.dev@outlook.com> writes:

> Hi,
>
> Here's another css-break question to queue into your "to-look-at" list. This time, I would like to understand whether the Gecko behavior is valid according to the fragmentation spec or not.
>
> The test case contain a single block element whose vertical padding makes it too tall for a fragmentainer. 
>
> Most browsers agrees that the break happens at the pixel line where the bottom padding starts to be too tall, but Firefox does make use a line break inside the block element itself in a way that looks odd to me.
>
> If you've some knowledge over fragmentation in html/css or some insight into gecko's layout procedures, your help could be valuable ;-)

I think Gecko is right, and that WebKit and Presto are wrong. Breaking
inside padding and borders should be avoided.

http://dev.w3.org/csswg/css-break/#possible-breaks

Gecko uses a class 2 opportunity (between the two line boxes). There are
no class 1 or 3 break opportunities in the test case.

-- 
---- Morten Stenshorne, developer, Opera Software ASA ----
---- Office: +47 23692400 ------ Mobile: +47 93440112 ----
------------------ http://www.opera.com/ -----------------
Received on Thursday, 18 July 2013 22:33:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:32 UTC