Mixin translate3d not translate3d?

[rainboxx]

Hi,

I'm not an expert in translate3d but I encountered an issue today with the translate3d mixin. Safari and other browsers don't understand transform: translate(0,0,0);, transform: translate3d(0,0,0); and the respectively prefixed variants are understood. Google search results are backing my finding.

See mixin in code: https://github.com/twitter/bootstrap/blob/master/less/mixins.less#L250

Was transform: translate(0,0,0); an old version I cannot find through Google or just a mistake?

Thanks

[mdo]

Check Google again—these exist and are used by browsers with prefixes as well. A few resources are the W3, http://caniuse.com/#feat=transforms2d, and http://www.the-art-of-web.com/css/css-animation/.

[rainboxx]

I cannot find a use of translate with 3 arguments at http://www.the-art-of-web.com/css/css-animation/. Also http://www.w3.org/TR/css3-2d-transforms/#two-d-transform-functions mentions only two arguments for translate while http://www.w3.org/TR/css3-2d-transforms/#three-d-transform-functions mentions translate3d, obviously, and not translate.

Am I missing something?

[rainboxx]

Maybe my first post was not clear...

Doesn't work: 2d translate with 3 arguments: transform: translate(0,0,0);
Result: Safari and Chrome strike this CSS line through.

Does work: 3d translate with 3 arguments: transform: translate3d(0,0,0);
Result: Safari and Chrome don't strike this CSS line through.