- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Wed, 12 Oct 2011 08:44:42 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Håkon Wium Lie <howcome@opera.com>, David Hyatt <hyatt@apple.com>, www-style@w3.org
On Oct 12, 2011, at 8:40 AM, Tab Atkins Jr. wrote: > 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. Are you sure about that? I would expect a grid of pages, as when printing from Excel or Adobe Illustrator.
Received on Wednesday, 12 October 2011 15:45:21 UTC