- From: David Hyatt <hyatt@apple.com>
- Date: Wed, 05 Oct 2011 15:12:39 -0500
- To: Alan Stearns <stearns@adobe.com>
- Cc: Vincent Hardy <vhardy@adobe.com>, "www-style@w3.org list" <www-style@w3.org>
On Oct 5, 2011, at 2:47 PM, Alan Stearns wrote: > On 10/5/11 12:35 PM, "Vincent Hardy" <vhardy@adobe.com> wrote: > >> >> On Oct 4, 2011, at 2:30 PM, David Hyatt 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. >>> >>> >> >> Hi Dave, >> >> After reading the all thread where you said you are fine with the current >> spec. and this initial email, I will add an action for met to be a bit more >> specific about the expected behavior. >> >> Thanks, >> Vincent > > There's a green section at the end of 4.4 that says "The 'overflow' property > is honored on a region..." Given the recent discussion I do not think this > is correct. When you add more detail to region-overflow:break you'll > probably need to remove the green section. Note that in the WebKit implementation at least, I made region-overflow:break only clip in the pagination direction. overflow:visible is still honored for content that spills out of the sides of the region. dave (hyatt@apple.com)
Received on Wednesday, 5 October 2011 20:13:08 UTC