- From: Vincent Hardy <vhardy@adobe.com>
- Date: Tue, 31 Jan 2012 04:35:49 -0800
- To: fantasai <fantasai.lists@inkedblade.net>
- CC: "www-style@w3.org" <www-style@w3.org>
Hi Fantasai, I have looked into this and discussed it with Alex, David Hyatt, Alan Stearns and our implementation team. There are various opinions. Our team believes that since we see regions as a low level building block, which, for example, could be used (internally) to implement multi-col, indeed, the rendering model should be no different and we could/should make the change you suggest. Alex thinks differently but I'll let him make his argument. Vincent. On Dec 27, 2011, at 1:58 AM, fantasai wrote: > # Regions create a new stacking context. [...] > # With regions, an element may be split across multiple regions and these > # regions may overlap (for example if they are absolutely positioned). > # So fragments of the same element can overlap each other. > # Since each element has a single z-index, it would be required to find > # another mechanism to decide in which order the fragments are rendered. > # Since each region creates a new stacking context, it is clear that each > # region is rendered separately and their rendering order follows the > # regular CSS rendering model. > > Fragments of the same element can overlap each other already due to inline > breaking, so this situation is not unique to regions. > > Unless there's some compelling reason why they should be different, I think > I'd rather regions "followed the regular CSS rendering model" as you say at > the end... and did not create a new stacking context unless other CSS > properties on the region dictated it. > > ~fantasai >
Received on Tuesday, 31 January 2012 12:36:15 UTC