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

[css3-multicol] overflow and paging?

From: Shelby Moore <shelby@coolpage.com>
Date: Mon, 11 Oct 2010 00:30:28 -0400
Message-ID: <84ac716c7a569e67bd67c0212886fe05.squirrel@sm.webmail.pair.com>
To: www-style@w3.org
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.

If I am viewing long multi-column content inside of a scrolling container,
I don't want to have to scroll that container all the way from the bottom
to top to read from one column to the next. Imagine that you don't flip to
the last page of a newspaper back to first page, just to read from bottom
of one column to the top of the next column.

Also, I don't want to see the end-most content before I am forced scroll
to see the content in the middle.

I think this is a major oversight in the current specification.  I hope
you will fix it.  Sorry to be frank, but as it is now, it makes my current
website look sloppy and wrong.

Realize I am not referring to paged media, where the entire browser window
is being broken into pages.  I am referring to an element within the page
which has its own vertical scroll page, which would include <iframe>.

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.

-Shelby Moore III
Received on Monday, 11 October 2010 04:30:55 UTC

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