- From: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
- Date: Thu, 10 Oct 2013 04:55:31 +0000
- To: Alan Stearns <stearns@adobe.com>, fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
> -----Original Message----- > From: Alan Stearns [mailto:stearns@adobe.com] > Sent: Monday, April 8, 2013 12:56 PM > > But in the case of a zero-height container where you have chosen to slice, > you're making no progress if you slice at the fragmentainer edge. I suppose > we could do a bit of both in that case (slice some minimum amount and have > it overflow) but I'd rather not *have* to do that, as in some cases where you > know more room is available later in the fragmentation context you can get a > much better effect by skipping the too-small fragment containers. > Fragmentation is a continuous process and as such it should guarantee progress for each fragmentation container (column, region, page etc.). What you're describing here is more of an error case rather than a use case and it should be dealt with as such. We propose that fragmentation containers are assumed to have a minimum of 1px height in order to guarantee continuity. With that assumption in place the rest of the fragmentation rules will apply and guarantee progress. Thanks, Rossen
Received on Thursday, 10 October 2013 04:56:01 UTC