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

Re: [css3-multicol] overflow and paging?

From: Andrew Fedoniouk <andrew.fedoniouk@live.com>
Date: Thu, 14 Oct 2010 23:07:57 -0700
Message-ID: <bay141-DS2036AD05C05C5D22B96089F8570@phx.gbl>
To: <shelby@coolpage.com>, <www-style@w3.org>
From: "Shelby Moore" <shelby@coolpage.com>
Sent: Sunday, October 10, 2010 9:30 PM
To: <www-style@w3.org>
Subject: [css3-multicol] overflow and paging?

> Seems to that when a container element on the page has overflow that
> scrolls vertically (e.g. <div style='overflow:auto'>), then any contained
> columns should be formatted as if they are paged media with a height equal
> to the clientHeight of container.
> I suppose there are cases where the intention is for the columns to not
> paginate on clientHeight of the vertically scrollable container, and thus
> I suggest you need to declare a new style setting, such as
> paginate-scrollable-contrainer, which defaults to inherit, where the
> document defaults to the whether the media type is paged.

I suspect that you want to see something like this:
with only difference that content inside is not scaled but rather has 
dynamic page
size determined by the container and paginated using that page size [1].

On the image you see document inside <frame type="pager"> - special 
attached to the <frame> that shows its content in print-preview mode.
Decorations of that frame and page boxes inside it is of CSS business.
But navigation, e.g. "next/previous page(s)" is a business of DOM/runtime.

I suspect that this is a better way of having columns in HTML/CSS.
It does not require changes in CSS rather than again flex units and the flow 
property (to replace page boxes) [2].

[1] http://www.terrainformatica.com/2010/02/printing-support-in-sciter/
[2] http://www.terrainformatica.com/w3/flex-layout/flex-layout.htm

Andrew Fedoniouk


Received on Friday, 15 October 2010 06:08:33 UTC

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