@@ -400,11 +400,6 @@ <h2 id=introduction><span class=secno>1. </span>Introduction</h2>
400400 behavior/role for the "transform" property and how is the other
401401 behavior/role indicated by a stylesheet author. If you have an opinion on
402402 this topic, please send feedback.</ div >
403-
404- < div class =issue > What do fixed backgrounds do in transforms? They should
405- probably ignore the transform completely, since - even transformed - the
406- object should be acting as "porthole" through which the fixed background
407- can be viewed in its original form.</ div >
408403 <!-- ======================================================================================================= -->
409404
410405 < h2 id =module-interactions > < span class =secno > 2. </ span > Module Interactions</ h2 >
@@ -603,6 +598,16 @@ <h2 id=transform-rendering><span class=secno>5. </span>The Transform
603598 go into more detail here about why fixed positioned objects should do
604599 this, i.e., that it's much harder to implement otherwise.
605600
601+ < p > < a href ="http://dev.w3.org/csswg/css3-background/#fixed0 "> Fixed
602+ backgrounds</ a > are affected by any transform specified for the root
603+ element, and not by any other transforms.
604+
605+ < p class =note > Thus an element with a fixed background still acts like a
606+ "porthole" into an image that's fixed to the viewport, and transforms on
607+ the element affect the porthole, not the background behind it. On the
608+ other hand, transforming the root element will still transform everything
609+ on the page, rather than everything except for fixed backgrounds.
610+
606611 < h3 id =transform-3d-rendering > < span class =secno > 5.1. </ span > 3D Transform
607612 Rendering</ h3 >
608613 <!-- Maybe define "tranform container" in the definitions, and use it everywhere
0 commit comments