- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Oct 2021 13:45:15 +0000
- To: public-css-archive@w3.org
Given that @smfr [said](https://github.com/w3c/csswg-drafts/issues/6238#issuecomment-867080924) he's OK with it, and given: 1. the note in the spec about improved performance/memory use, 2. that it's what Gecko and Chromium currently do, and 3. that, given that the 3D context behavior in the spec also matches the Gecko/Chromium behavior and not the WebKit behavior, it seems like it's likely the more Web-compatible behavior. I'm going to change the editor's draft to specify it this way. In particular, to expand on (3) a little bit: Given that, in the presence of preserve-3d (or even without it!) WebKit will perform 3D intersection one element in the tree higher (closer to the root) than the spec says to (and what Chromium and Gecko do), it seems that specifying the WebKit behavior *along with* the spec's current 3D intersection model has a chance of breaking content, since it would move backgrounds (such as those in test 004.tentative in web-platform-tests/wpt#31375) from being 3D intersected with in all engines to being behind the 3D scene. And given point (1) it seems like there's an advantage to doing things this way, so I think it's probably best to do so. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6238#issuecomment-951955924 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 October 2021 13:45:18 UTC