W3C home > Mailing lists > Public > www-style@w3.org > September 2011

RE: [css3-page] Rules for Pagination into Varying-Width Pages

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Tue, 27 Sep 2011 00:51:53 +0000
To: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928412271F43@TK5EX14MBXC212.redmond.corp.microsoft.com>
I haven't seen this thread yet... 

I like these rules. A couple more issues to consider:

-- Margin/border/padding - are these calculated once per element or per page? 
(I think per page, it is rare to have percentage in any of them, but if it ever happens it is more likely that per-page will work better)

-- What happens when an image with "width:100%; height:auto" is broken across pages of different width?
(I think it is rendered with different scale on different pages. It would probably look better to keep image scale from starting page, but the use case is rare and consistency seems more valuable)

Alex

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of fantasai
Sent: Monday, September 19, 2011 10:15 AM
To: www-style@w3.org
Subject: [css3-page] Rules for Pagination into Varying-Width Pages

Rules:

   * Layout is performed per-page, with each page continuing progress from the
     breakpoint on the previous page, but recalculating sizes assuming an initial
     containing block of the current page size.
   * Intrinsic sizes are calculated and maintained across the entire element. Where an
     ICB size is needed, assume an initial containing block of the starting page's size.
   * Continuations of boxes on a previous page must start at the top of the page.
     If this results in multiple shrinkwrapped floats side-by-side that would otherwise
     be staggered (if they were not continuations), the floats' widths are reduced
     in proportion to their original widths until they fit. However they are not
     reduced past their min-content width; this may result in overlap between left and
     right floats or side-by-side left floats overflowing the containing block.

Implications:

   * Boxes (including tables) fullfilling layout constraints at their fill-available
     size will change widths across pages.
   * Boxes (including tables) fulfilling layout constraints at their min-content,
     max-content, or fixed-width size will maintain their width across pages.
   * Floats might overlap if, e.g. a left float and a right float both begin on a
     wide page, but their min-content or fixed-width measures taken together are too
     wide to fit on the second, narrower page. (They will not overlap if only their
     max-widths are too wide, since the shrinkwrap adjustment will give them narrower
     widths.)

~fantasai
Received on Tuesday, 27 September 2011 00:52:22 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:44 GMT