This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15784 - How to deal with intersecting geometry must be specified
Summary: How to deal with intersecting geometry must be specified
Status: RESOLVED FIXED
Alias: None
Product: CSS
Classification: Unclassified
Component: Transforms (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Simon Fraser
QA Contact:
URL:
Whiteboard:
Keywords:
: 15783 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-01-30 00:32 UTC by Gregg Tavares
Modified: 2012-03-07 05:07 UTC (History)
6 users (show)

See Also:

Attachments

Description Gregg Tavares 2012-01-30 00:32:55 UTC 
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
Comment 1 Simon Fraser 2012-01-30 09:38:33 UTC 
Does the new text in <http://dev.w3.org/csswg/css3-transforms/#transform-3d-rendering> help?
Comment 2 Aryeh Gregor 2012-02-07 18:08:18 UTC 
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).
Comment 3 Aryeh Gregor 2012-02-22 21:23:12 UTC 
*** Bug 15783 has been marked as a duplicate of this bug. ***
Comment 4 Simon Fraser 2012-02-29 17:40:46 UTC 
We resolved on the call today to make the intersection behavior required.
Comment 5 Simon Fraser 2012-03-07 05:07:04 UTC 
Fixed in 4abce06156b6c794712490459e194977e908dda1.