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

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

From: Brad Kemper <brad.kemper@gmail.com>
Date: Wed, 12 Oct 2011 17:52:44 -0700
Message-Id: <C1D1044F-C59E-4252-9ACC-4DE74C549003@gmail.com>
Cc: David Hyatt <hyatt@apple.com>, "www-style@w3.org list" <www-style@w3.org>
To: Håkon Wium Lie <howcome@opera.com>
On Oct 12, 2011, at 3:12 PM, Håkon Wium Lie <howcome@opera.com> wrote:

>> Just to follow up on this, another reason I think the page size
>> should be independent of the size of the box is that in iBooks
>> landscape mode we show two pages at once. Right now the fact that
>> we happen to use a multi-column strip allows us to just show two
>> "columns" since each "column" is in reality a page, but that just
>> totally falls apart for writing modes like vertical-rl (where the
>> column layout by default is in a vertical strip instead, but a 2-up
>> display still needs to be a horizontal strip).
> The 'paged-x' concept seems to match your requirement; it lays pages out
> in horizontal strips no matter what writing direction is used in the pages.

But by being a value for 'overflow', doesn't it override both 'overflow-x' and 'overflow-y'? So that whichever one is in the inline direction defaults back to 'visible'? 

Imagine a paged e-book about JavaScript or CSS that had some long lines of code that shouldn't be broken. I was imagining an author might want to do something like this:

overflow: auto /* takes care of x and y */; overflow-block-prog-dir: paged-inline-dir;

That way (ignoring for now how long it is too write), you could cause the extra pages to be arrayed in a strip in the inline progression direction, and have automatic scrollbars in the inline direction when an unbreakable line got too long. this also has good fallback. 

OR, maybe better yet, keep it as a value for overflow, but have overflow be a shorthand for three values:

overflow: <overflow-x> <overflow-y> <overflow-block-progression-direction>

(not fleshed out with square brackets and pipes and question marks, but...) then an author might write:

overflow: auto; /* fallback */
overflow: auto paged;

When i think about it, it seems like we don't need paged-x to create something similar to multi-col. If we have paging control UI (even like iBook's magic page flipping), then the other pages should hidden (like display: none), not laid out in a horizontal strip or inline-direction strip. 
Received on Thursday, 13 October 2011 00:53:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:05 UTC