Input wanted: should we change the force3D default?

[dxc]

As long as we get to turn it off if we want to, which it sounds like you're planning on doing, I'm happy. I heart GS.

[Rodrigo]

HI,

 

Great idea and discussion guys!!

 

+1 for the "auto" feature, is smart and doesn't stick around after the instance is over, ME LIKE IT!!

[Jean-Baptiste Janot]

Hi !

If using "auto" or "true", what if the browser can't handle 3D ? Does it keep a 2D tween, or does it try to use a 3D tween anyway ?

Is it on our hand to test for it ?

 

"auto" by default seems great by the way.

[Jonathan]

Hello Hypolythe,

 

GSAP will detect for you if CSS 3D or 2D Transforms are supported in the current browser. GSAP will do all the heavy lifting for you so you can concentrate on animating and not cross browser compatibility. If GSAP does not detect CSS 3D transforms it will fallback, and use CSS 2D transforms instead. GSAP can basically animate any object or property!

 

Does that help Hypolythe?

 

[Jean-Baptiste Janot]

Of course that helps

Thanks again Jonathan !

[GreenSock]

Yep, Jonathan is exactly right. GSAP will be "smart" about when it applies the 3D GPU juicing. It'll just use 2D transforms in browsers that don't support it. 

[GreenSock]

Thanks for all the input, guys. Version 1.15.0 was launched and it's got these features enabled. Yay!