W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: [css3-regions] regions forming stacking contexts

From: Brad Kemper <brad.kemper@gmail.com>
Date: Thu, 2 Feb 2012 06:50:33 -0800
Message-Id: <A57B29B9-292D-4324-9097-7E7BCC1452C3@gmail.com>
Cc: "robert@ocallahan.org" <robert@ocallahan.org>, "www-style@w3.org Style" <www-style@w3.org>
To: Alex Mogilevsky <alexmog@microsoft.com>


Sent from my iPad

On Feb 2, 2012, at 2:55 AM, Alex Mogilevsky <alexmog@microsoft.com> wrote:

>> From: rocallahan@gmail.com [mailto:rocallahan@gmail.com] On Behalf Of Robert O'Callahan
>> Sent: Thursday, February 02, 2012 2:12 AM
>> 
>> Here's another example of questions arising from the latter. Consider two regions R1 and R2, 
>> where R1 is position:relative and R2 is position:static, and we flow content into the regions 
>> containing an element that's position:absolute. How do we determine the abs-pos containing 
>> block of the element? Is it possible for the element to split into multiple boxes with different 
>> containing blocks? Could a simple layout change, such adding some text to the DOM before the
>> abs-pos element, push the abs-pos element from R1 to R2 and thus change its containing block?
> 
> Well, I will wholeheartedly agree that separate stacking context per region is a good way to preserve sanity.
> 
> Different positioning for regions shouldn't be a problem though. The initial containing block for named flow is the first region. Not sure it is clearly defined now, but it is that way in paged media (first page is the ICB) and it better be same in regions.

And multi-col?

> And I don't even want to think of abs pos elements in regions not being positioned inside regions (which could possibly be considered with this line of thinking).

You mean if the positioned content is bigger than the region? For paged media, it gets sliced up into the multiple pages, right? I don't think multi-col handles it that way though, does it? 
Received on Thursday, 2 February 2012 14:51:03 GMT

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