- From: Håkon Wium Lie <howcome@opera.com>
- Date: Sun, 4 Jan 2009 23:08:48 +0100
- To: "Giovanni Campagna" <scampa.giovanni@gmail.com>
- Cc: www-style@w3.org
Also sprach Giovanni Campagna:
> There are two ways to implement that use-case into current CSS
>
> 1) One <div> per page, and some DOM manipulation (visibility or display,
> with additional keys events)
Inserting <div>s is not a solution -- you wouldn't know where to
insert them as the size and number of pages will vary depending on the
viewport.
> 2) One <div>, fixed positioned, which contains the big content (and columns,
> heading, what you want)
> you can use
> overflow:visible;
> and scroll page-by-page focusing on content then PgUp / PgDn, or using the
> custom buttons that in turns calls scrolling CSSOM API
This gets rid of the scrollbars, but the presentation is still not
page-based. For example, browsers will still show a horizonally split
line at the bottom of the viewport.
I want the browser to know that it's in a paged mode and not show
half-lines at the bottom; rather, the line will be moved to the next
page.
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Sunday, 4 January 2009 22:09:26 UTC