RE: [css3-break] Empty fragmentainers

> -----Original Message-----
> From: fantasai [mailto:fantasai.lists@inkedblade.net]
> Sent: Monday, January 13, 2014 2:54 PM
> >
> > It's clearer, but not necessarily better :) Since now there's only a
> > recommendation about "Break as few times as possible" (SHOULD? MAY?)
> > it will make things harder to test with regard to interoperability. In
> > a scenario with one small region and one big region, should content
> > that doesn't fit in the small region create an empty region and be
> > flowed in the big one? How about if we have 3 small regions and a big
> > one? How about 10 small regions and one big region?
> > Past which point the recommendation to not overflow the region takes
> > precedence over "break as few times as possible"?
>
> I don't know what to do here. :) Should we remove that sentence or replace
> it with something like "Don't break if it's not necessary to fit content within
> the fragmentainer"? I think we don't have that sentence for line breaking,
> and it's kindof obvious, so I don't mind not putting it in... but what would
> *you* like to see there?

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, 15 January 2014 18:53:25 UTC