Transitions do not use3DByDefault when it is available.

[geek-caroline]

There is a property:

    use3DByDefault

and this is set to be true which is what I want (this issue stems from me finding only this translate3d is optimised on the iPad).

However, if one does not specify at the time of calling a transition that one wants to use 3D, it seems to me that it will never be used.

At line 344 the implementation of getTranslation:

    return ((use3D === true || (use3DByDefault === true && use3D !== false)) && has3D) ? 'translate3d(' + x + 'px, ' + y + 'px, 0)' : 'translate(' + x + 'px,' + y + 'px)';

in essence, due to the calling process it actually means:

• use3D must be true (but am not passing this in as am expecting it to occur by default)
• use3DByDefault && use3D && has3D

as there is a test to see whether useTranslate3d was passed in as a property in the chain of calls leading to this test and if it was not this value is set to false:

_applyCSSTransition(
    ....
    prop.useTranslate3d === true);

meaning that in essence the two queries in getTranslation become redundant as either use3D is explicitly declared or will be false?

[benbarnett]

Thanks for the detailed report