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

Re: [css3-regions] regions forming stacking contexts

From: Vincent Hardy <vhardy@adobe.com>
Date: Wed, 1 Feb 2012 00:19:48 -0800
To: "robert@ocallahan.org" <robert@ocallahan.org>
CC: "www-style@w3.org Style" <www-style@w3.org>
Message-ID: <CB263E05-BDAE-43F5-AD4C-FAF3848A08E6@adobe.com>
Hi Rob,

I have created a bug to track the issue your raised in this email and previous one and added a marker for the issue in the spec. that will soon be committed.


I also created a bug to track the question of whether or not regions form a stacking context:



On Feb 1, 2012, at 5:05 AM, Robert O'Callahan wrote:

On Sat, Jan 7, 2012 at 1:16 AM, Alex Mogilevsky <alexmog@microsoft.com<mailto:alexmog@microsoft.com>> wrote:
Region is a viewport, anything visible within a region should behave the same way as if it was on screen scrolled to that point. There may be exceptions due to really complicated cases but in general it should work the same, shouldn’t it?

No. The problem I referred to in my previous email occurs when different parts of an element are visible in two or more different regions at the same time. The semantics of 'opacity' and 'filter' (among other properties) on the element demand that the entire contents of the element be rendered as a unit, which will be impossible if the regions are in different stacking contexts.

There is no analogous issue with viewports since an element can't appear simultaneously in multiple viewports.

"If we claim to be without sin, we deceive ourselves and the truth is not in us. If we confess our sins, he is faithful and just and will forgive us our sins and purify us from all unrighteousness. If we claim we have not sinned, we make him out to be a liar and his word is not in us." [1 John 1:8-10]
Received on Wednesday, 1 February 2012 08:20:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:11 UTC