W3C home > Mailing lists > Public > www-style@w3.org > January 2009

Re: [css3-gcpm] new draft -- including "overflow: paged"

From: Giovanni Campagna <scampa.giovanni@gmail.com>
Date: Sun, 4 Jan 2009 23:27:48 +0100
Message-ID: <65307430901041427p6e205f46t5e45501868c09484@mail.gmail.com>
To: "Håkon Wium Lie" <howcome@opera.com>, www-style@w3.org
As I wrote later, I finally discovered what you meant.

So we have two possibilities:

1) The whole webpage is displayed paged (but some pieces, including
navigation, are not scrolled, because of paged-media css)
In this case you don't need a overflow:paged;
beacuse overflow:paged affects only one element of the page (you wrote
<body> in your example, but also :root would suffer from the same problem,
unless we put some more magic to :root or html body elements)
Instead you need a way to force the UA from continuous to paged media, like
Opera does pressing F11 (switching from screen to projection)
I.e. you need to change, by means of scripting or something else, the media
according to which the page should be rendered (in this case the "media" is
intended as just a subset of CSS properties that UA allows in certain
situations)
It would be the same situation as "do a print preview" (switch to print
media, but display on the screen)

2) Ony one block is the page, all the rest is flowed
You can partly workaround this using overflow: scroll (sorry i wrote visible
i meant scroll) or, if UA implemented this, using overflow:hidden and JS
scrolling
For what instead concerns page number, heading, and the like, I think it
should not be possible to display them inside the paged block, because it
would conflicts with their behaviour on native paged user agents, which
instead would display them relative to the real page
Received on Sunday, 4 January 2009 22:28:23 GMT

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