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

Re: [css3-gcpm] paged presentations, page floats, paged navigation between documents

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 12 Oct 2011 08:40:38 -0700
Message-ID: <CAAWBYDCzvbPnFf8iTrXR-UuAMcBo-WDEUbh-BPDE7Od=zCrFCA@mail.gmail.com>
To: Håkon Wium Lie <howcome@opera.com>
Cc: David Hyatt <hyatt@apple.com>, www-style@w3.org
On Wed, Oct 12, 2011 at 8:30 AM, Håkon Wium Lie <howcome@opera.com> wrote:
> Also sprach Tab Atkins Jr.:
>  > So, which direction of overflow becomes paged, the block or inline
>  > axis? Or the horizontal or vertical axis? The fact that you used
>  > large columns in your example implies that pages are always
>  > generated from the overflow in the inline axis.
> Think of it as printed paper sheets. Say, a document is printed onto
> three sheets. Then you lay those sheets out onto the floor, either
> along the x/horizontal axis, or the y/vertical axis.
> The GCPM paged-* values don't specify how the content should be
> printed onto those three sheets, but it specifies that (a) there
> should be sheets and (b) which direction those sheets should be laid
> out.

If it doesn't specify, then that's just confusing.  What happens if
content overflows in both directions?

Paged Media currently always sends the block-axis overflow (or
vertical-axis, I dunno which) to the next page.  Inline (/horizontal)
overflow is hidden.  Presumably this should work the same.

Received on Wednesday, 12 October 2011 15:41:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:51 UTC