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

Overflow-x/overflow-y – it’s a good point. It is possible to define what all combinations mean where only one of the two is ‘paged’ but for implementation I would very much rather prefer that they are required to both be ‘paged’ or not in CSS3…

From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Robert O'Callahan
Sent: Sunday, January 04, 2009 3:28 PM
To: Håkon Wium Lie
Cc: www-style@w3.org
Subject: Re: [css3-gcpm] new draft -- including "overflow: paged"

On Mon, Jan 5, 2009 at 7:34 AM, Håkon Wium Lie <howcome@opera.com<mailto:howcome@opera.com>> wrote:
 - a new section "Creating paged presentations" bas been added. It
   suggests that it should be possible to express preference for
   page-based presentation by saying:

     body { overflow: paged }

   Or something. This would apply to non-paged media (e.g., screen)
   to get rid of the scrollbar.

That was confusing. You might still want a scrollbar, or something very like a scrollbar, to traverse pages. We certainly need overflow:paged to allow the UA to reserve space for UI.

BTW shouldn't this be defined as a value for overflow-x/overflow-y with 'overflow' as shorthand?

Rob
--
"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]