15784 2012-01-30 00:32:55 +0000 How to deal with intersecting geometry must be specified 2012-03-07 05:07:04 +0000 1 1 1 Unclassified CSS Transforms unspecified All All RESOLVED FIXED P2 normal --- 1 gman smfr ayg cmarrin dino dschulze eoconnor smfr oldest_to_newest 63308 0 gman 2012-01-30 00:32:55 +0000 Designers will not be able to get reproduce-able results across browsers unless this is specified. Examples of this problem now, see the difference between Chrome and Safari's rendering of 3 intersecting planes. http://greggman.com/downloads/examples/correct-3d-css-polygon-sorting-subdivisions-safari.png http://greggman.com/downloads/examples/incorrect-3d-css-polygon-sorting-subdivisions-chrome.png 63317 1 smfr 2012-01-30 09:38:33 +0000 Does the new text in <http://dev.w3.org/csswg/css3-transforms/#transform-3d-rendering> help? 63854 2 ayg 2012-02-07 18:08:18 +0000 Could we change the "should" to a "must"? "Should"s are bad for interop. Currently I think only Safari gets this right (reportedly -- I haven't been able to test). 64462 3 ayg 2012-02-22 21:23:12 +0000 *** Bug 15783 has been marked as a duplicate of this bug. *** 64739 4 smfr 2012-02-29 17:40:46 +0000 We resolved on the call today to make the intersection behavior required. 65090 5 smfr 2012-03-07 05:07:04 +0000 Fixed in 4abce06156b6c794712490459e194977e908dda1.