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

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

From: Håkon Wium Lie <howcome@opera.com>
Date: Wed, 12 Oct 2011 21:03:28 +0200
Message-ID: <20117.58496.224426.900632@gargle.gargle.HOWL>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: David Hyatt <hyatt@apple.com>, www-style@w3.org
Also sprach Brad Kemper:

 > >> 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.
 > > 
 > > Yes, it should work the same. But it should only be specified in one place. 
 > 
 > So, do we need an 'overflow-block-axis' that overrides 'overflow-x'
 > or 'overflow-y' depending on the block progression direction?

I don't understand what we would use it for. 

Opera's implementation is, in principle, quite simple. We reuse the
multicol code and lay out the content of the element according to:

  http://www.w3.org/TR/css3-multicol/#pagination-and-overflow-outside-multicol

Now, if 'overflow: paged-*' is set (instead of 'overflow: visible' in
the example), we create new pages from the overflow columns. These new
pages are laid out according to the paged-* value. For example, if the
language is RTL and 'overflow: paged-x' is set, pages are laid out
leftwards. If 'overflow: paged-y' is set, pages are laid out downwards.

I don't see a need for a new property to achieve what I want. Am I
missing something?

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Wednesday, 12 October 2011 19:04:08 GMT

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