Jump to content


will-change property

Warning: Please note

This thread was started before GSAP 3 was released. Some information, especially the syntax, may be out of date for GSAP 3. Please see the GSAP 3 migration guide and release notes for more information about how to update the code to GSAP 3's syntax. 

Recommended Posts

Hi Rob,


Yeah, we've read that article, its VERY informative. Thanks for sharing. Right now we would still have to do quite a bit of testing to see how and where this can benefit the platform. 


As the author noted, doing too many will-changes can be bad and its also important to remove them. Not so sure at this point if this is something the engine should handle automatically, the engine should have hooks for or we just leave it up to the developer. 


Its definitely worth investigating, yet will take some time. Also important to consider is how all the other browsers will implement this. It seems right now that its quite vague exactly what the browser is doing behind the scenes.


For now you can use the force3d property in a tween to push the target to its own gpu layer, which most often yields some nice performance gains:


  • Like 2
Link to comment
Share on other sites

Thanks for the answer, and good to here that you are on top of it - as always :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.