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

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

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Sun, 4 Jan 2009 15:52:56 -0800
To: "robert@ocallahan.org" <robert@ocallahan.org>
CC: Håkon Wium Lie <howcome@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <7C2F64B551D8664AAD94A28DAC37D0206B53334710@NA-EXMSG-C103.redmond.corp.microsoft.com>
I don’t disagree. My implementation concerns are around UI, not layout. But I guess if it is to deal with otherwise unusable pages, I can set aside the dislike to scrollbars and let them help…

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

On Mon, Jan 5, 2009 at 12:38 PM, Alex Mogilevsky <alexmog@microsoft.com<mailto:alexmog@microsoft.com>> wrote:

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…

I actually think overflow-x:scroll; overflow-y: paged; would be quite useful.

"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]
Received on Sunday, 4 January 2009 23:53:39 UTC

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