- From: mattwoodrow via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Feb 2019 21:18:36 +0000
- To: public-css-archive@w3.org
I wrote up an explanation of how Gecko interprets the spec and how the implementation works, along with a bunch of testcases to show some of the differences: https://docs.google.com/document/d/1yb4a_uhTG3KmcbGPta4B9p67v1HO_qY8ZMk-otGOwTc It looks like the primary difference is that WebKit considers a flattening element (element with a flattening property, or stacking context with transform-style:flat) to be what establishes a 3d rendering context for its children (but not itself), whereas both Gecko and blink consider an element with transform-style:preserve-3d to be what establishes a 3d rendering context for itself and its children. I think the blink/Gecko interpretation will be simpler to specify, since the root of the 3d rendering context needs to be a stacking context to create a flattened representation. Flattening properties (like overflow:scroll) aren't necessarily a stacking context, so we'd need to make them one, if (and only if) they happen to have 3d descendants. In Gecko/blink the root always has transform-style:preserve, which is explicitly a stacking context. Commenting here since the css-meeting bot did, but this is effectively the same underlying issue as #3138, #1944, #1951 and #1952. -- GitHub Notification of comment by mattwoodrow Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1950#issuecomment-468442155 using your GitHub account
Received on Thursday, 28 February 2019 21:18:37 UTC