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

Re: [css-regions] The region-overflow property

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 4 Oct 2011 15:01:39 -0700
To: David Hyatt <hyatt@apple.com>, "www-style@w3.org list" <www-style@w3.org>
Message-ID: <CAB0D053.7FEF%stearns@adobe.com>
On 10/4/11 2:30 PM, "David Hyatt" <hyatt@apple.com> wrote:

> On Oct 4, 2011, at 1:23 PM, David Hyatt wrote:
> 
>> http://dev.w3.org/csswg/css3-regions/#region-overflow
>> 
>> It is ambiguous (to me at least) in section 4.4 whether region-overflow:break
>> causes clipping to occur when content spills out of the last region. I am
>> assuming the only thing it affects is pagination at the last region edge, and
>> that clipping is always controlled by overflow.
>> 
> 
> Actually upon re-reading this, it sounds like you do expect the content that
> paginates as a result of region-overflow:break to be into some unrendered
> space when region-overflow:break is specified. That seems like fine behavior
> to me, but it should probably be specified a bit more clearly in the text.

My take on the region-overflow property is that it's an override to the
regular overflow property. If region-overflow is set to auto, then
whatever's specified in overflow happens. But if region-overflow is set to
break, then:

1. the overflow property is ignored
2. the last region will use pagination to break
3. any overflow content will not display

The main (only?) difference between 'overflow:hidden' and
'region-overflow:break' is that the latter will not display a clipped
portion of a line box (or anything else that would normally get pushed to
the next paginated region).

If my interpretation is correct, then it might be better to add a new
"break" value to the overflow property. But this would require implementing
pagination breaks on non-regions.

Alan
Received on Tuesday, 4 October 2011 22:02:09 GMT

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