Looks like Chrome has been fixing this bug itself at some point, making the -webkit-transform: translate3d(0,0,0) fix actually forces it render as if it is position: absolute; instead of position: fixed;.
Could anyone confirm this? Or is it me who messed the CSS up?
Looks like Chrome has been fixing this bug itself at some point, making the
-webkit-transform: translate3d(0,0,0)fix actually forces it render as if it isposition: absolute;instead ofposition: fixed;.Could anyone confirm this? Or is it me who messed the CSS up?