File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change 1+ 2012-07-12 simon.fraser@apple.com
2+ Fix https://www.w3.org/Bugs/Public/show_bug.cgi?id=17431 by making the wording
3+ about the rendering effects of 3D transforms not CSS-specific.
4+
152012-07-12 simon.fraser@apple.com
26 Move Chris Marrin and Dave Hyatt to Former Editors (with their approval).
37 Fix https://www.w3.org/Bugs/Public/show_bug.cgi?id=17521, adding text about treatment
Original file line number Diff line number Diff line change @@ -496,11 +496,11 @@ <h3 id="transform-3d-rendering">3D Transform Rendering</h3>
496496 </ p >
497497 < p >
498498 Three-dimensional transforms can result in transformation matrices with a non-zero
499- Z component<!-- clarify --> , potentially lifting them off the plane of their
500- containing block. Because of this, elements with three-dimensional transformations
501- could potentially render in an front-to-back order that different from the normal CSS rendering order ,
502- and intersect with each other. Whether they do so depends on whether the element is a member
503- of a < span class ="term "> 3D rendering context</ span > , as described below.
499+ Z component (where the Z axis projects out of the plane of the screen). This can result
500+ in an element rendering on a different plane than that of its containing block. This
501+ may affect the front-to-back rendering order of that element relative to other elements ,
502+ as well as causing it to intersect with other elements. This behavior depends on whether the
503+ element is a member of a < span class ="term "> 3D rendering context</ span > , as described below.
504504 </ p >
505505 < div class ="issue ">
506506 < p class ="desc "> This description does not exactly match what WebKit implements. Perhaps
You can’t perform that action at this time.
0 commit comments