Breaks position:fixed; in Chrome and Safari

[olivierbeaulieu]

This guy here :

body {
-webkit-transform: translate3d(0,0,0);
}

Breaks position:fixed in Chrome and Safari, making it behave like it was position:absolute

[daneden]

Yup.

From the W3C:

"Any value other than ‘none’ for the transform results in the creation of both a stacking context and a containing block. The object acts as a containing block for fixed positioned descendants." (http://www.w3.org/TR/css3-2d-transforms/)

THIS is why I didn't implement hardware acceleration this way. I knew there was a reason. I guess we turn it back?

[Ahrengot]

yeah, that thing does some wierd stuff. Also messes up image sprites in Chrome (Generated via Compass).

[vjpr]

+1