RESOLVED INVALID 54745
-webkit-transform: translate3d(0,0,1) fails to affect z-index of layer 
https://bugs.webkit.org/show_bug.cgi?id=54745
Summary -webkit-transform: translate3d(0,0,1) fails to affect z-index of layer
W. James MacLean
Reported 2011-02-18 06:48:03 PST
-webkit-transform: translate3d(0,0,1) fails to affect z-index of layer
Attachments
Patch (8.92 KB, patch)
2011-02-18 06:52 PST, W. James MacLean 		jamesr: review-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
W. James MacLean
Comment 1 2011-02-18 06:52:48 PST
Created attachment 82956 [details] Patch
James Robinson
Comment 2 2011-02-18 10:34:18 PST
This renders correctly without your patch. 3d transforms do not affect the z-index property and do not change the global ordering outside of a -webkit-preserves-3d block.
W. James MacLean
Comment 3 2011-02-18 11:09:50 PST
(In reply to comment #2) > This renders correctly without your patch. 3d transforms do not affect the z-index property and do not change the global ordering outside of a -webkit-preserves-3d block. Hmmm, OK. 1) What platform did you try on? This does not render properly (i.e. the blue box is in front) on Chrome on linux. 2) Since both divs are presumably opaque, should the closer one be on top? This patch is in response to http://code.google.com/p/chromium/issues/detail?id=63781 Is the original bug asking for something incorrect then?
James Robinson
Comment 4 2011-02-18 11:59:26 PST
Chrome's rendering (blue on top) is correct. Since the two transformed divs are siblings and do not share any transformed ancestors, they can be thought of as living in separate 3d spaces (see http://www.webkit.org/blog/386/3d-transforms/). The rendering is determined based on the CSS stacking order. Since the blue div appears later in the document it paints on top. There is a bug in Safari here, would you mind checking if that is on file and filing a new bug if not (smfr and cmarrin would be good to CC)?
W. James MacLean
Comment 5 2011-02-18 12:01:50 PST
(In reply to comment #4) > Chrome's rendering (blue on top) is correct. Since the two transformed divs are siblings and do not share any transformed ancestors, they can be thought of as living in separate 3d spaces (see http://www.webkit.org/blog/386/3d-transforms/). The rendering is determined based on the CSS stacking order. Since the blue div appears later in the document it paints on top. > > There is a bug in Safari here, would you mind checking if that is on file and filing a new bug if not (smfr and cmarrin would be good to CC)? Will do ... thanks!
Note You need to log in before you can comment on or make changes to this bug.