W3C home > Mailing lists > Public > www-style@w3.org > February 2014

Re: [css3-break] Empty fragmentainers

From: Mihai Balan <mibalan@adobe.com>
Date: Wed, 5 Feb 2014 17:54:22 +0000
To: Rossen Atanassov <Rossen.Atanassov@microsoft.com>, fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CF184606.26C37%mibalan@adobe.com>
Hi fantasai, Rossen,
I finally managed to read through the initial thread about pathological
fragmentation.
You're right - it's basically the same problem. However, it's unclear to
me what the conclusion at that point was.
So I think it would be good to have a section in the fragmentation spec
about how not to leave empty fragmentainers :)

Thanks,
m.

Mihai Balan | Quality Engineer @ Web Engine team |  mibalan@adobe.com |
+4-031.413.3653 / x83653 | Adobe Systems Romania



On 1/15/14 8:52 PM, "Rossen Atanassov" <Rossen.Atanassov@microsoft.com>
wrote:

>>We can certainly drop the sentence here but I don't think this will help
>>anything. Mihai's interpretation suggests that empty regions
>>(fragmentainers) are created due to fragmentation. "should content that
>>doesn't fit in the small region create an empty region and be flowed in
>>the big one?" - this behavior would suggest that a fragmentainer is left
>>empty - to me this is the conversation we had about "pathological
>>fragmentation" [1].
>
>One criteria that I realize we're missing in this section is "Don't leave
>fragmentainers empty". Mihai what do you think?
>
>Rossen
>
>[1] http://lists.w3.org/Archives/Public/www-style/2013Oct/0337.html
Received on Wednesday, 5 February 2014 17:54:56 UTC

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