W3C home > Mailing lists > Public > public-fx@w3.org > October to December 2011

Re: [3d-transforms] Behavior of intersecting layers with transform-style: preserve-3d is undefined and inconsistent across implementations

From: Gregg Tavares (wrk) <gman@google.com>
Date: Sat, 8 Oct 2011 16:20:26 -0700
Message-ID: <CAKZ+BNq++ePEyEzDS+_CJ=VseOM513Zwi2VW2NweOCESiMeY-A@mail.gmail.com>
To: Simon Fraser <smfr@me.com>
Cc: Chris Marrin <cmarrin@apple.com>, James Robinson <jamesr@google.com>, public-fx@w3.org
On Fri, Oct 7, 2011 at 8:13 PM, Simon Fraser <smfr@me.com> wrote:

> On Oct 7, 2011, at 7:48 PM, Gregg Tavares (wrk) wrote:
> I don't know if this belongs in a separate thread but even before
> intersection we need to spec how things get sorted. Mid point?, front most
> point?, back most point?, local origin?
> Here's an example of just sorting where Chrome and Safari don't currently
> match
> http://greggman.com/downloads/examples/3d-css-sorting-issue.html
> Screenshots if you don't want to run another browser
> http://greggman.com/downloads/examples/3d-css-sorting-issue-chrome.png
> http://greggman.com/downloads/examples/3d-css-sorting-issue-safari.png
> In this testcase #over should render on top, even in the absence of 3D
> transforms. It would do so with just the position:absolute. The z-index is
> extra insurance. Chrome's rendering is obviously incorrect.

Is that clear from the spec? If set over to "transform: translateZ(-1px);"
is it still on top because of the "z-index: 2" or not?

> Simon
Received on Saturday, 8 October 2011 23:21:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 8 October 2011 23:21:02 GMT