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

[css3-break] Empty fragmentainers

From: Mihai Balan <mibalan@adobe.com>
Date: Wed, 4 Dec 2013 13:41:29 +0000
To: "WWW Style (www-style@w3.org)" <www-style@w3.org>
Message-ID: <32E5AE8565CC6142BA0AAFA5A95697E04D2D6A98F3@eurmbx01.eur.adobe.com>
Hello everybody,

I have a question related to how "far" should content be pushed during fragmentation. Currently the Fragmentation spec states that:
    When multiple forced break values apply to a single break point, they combine such that all types of break are honored and no content-empty page boxes are generated, except for at most one content-empty page as may be required by the forced break values to position ensuing content on a specific type of page.

Does a similar recommendation holds for non-page fragmentation containers? More specifically:
a. when fragmenting through non-page fragmentation containers, must the UA still try to produce **no** content-empty fragmentation containers?
b. In doing so, what would be the acceptable behavior (e.g. overflow?) and what would be unacceptable behavior (e.g. slicing, multiple content-empty fragmentation containers, etc.)

Whatever the answers to these questions are, I think they should be clearly stated in the spec as to minimize confusion. Right now, that section of the spec can be read either as applying to pages only but also as an implied recommendation for other types of fragmentation containers.

Does it make sense?
Mihai
 
Mihai Balan | Quality Engineer @ Web Engine team |  mibalan@adobe.com | +4-031.413.3653 / x83653 | Adobe Systems Romania
Received on Wednesday, 4 December 2013 13:41:58 UTC

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