We now all know, particularly from that nice article, that we should prefer css-transforms to animate position.
But we got the choice between translate()
an
As cameron suggested translate3d
should be faster in a lot of browsers, mostly those that use gfx hardware acceleration to speed up rendering. especially on webkit translate3d
was the prefered way of forcing hardware acceleration on page items.
though in mit experience sometimes there is one drawback to using 3d transforms - in certain browser-versions/os combinations (osx+safari i'm looking at you) hardware accelerated rendering can slightly alter font smoothing as well as interpolation thus causing minor flicker or blur. those situations can mostly be worked around but should be kept in mind.