Jump to content
Search Community

Chrome 49 - Janky GSAP

joe_midi test
Moderator Tag

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

  • 5 months later...



i used the workaround since then for scaling background images in css and helped me a lot with better image quality.

-webkit-backface-visibility: hidden;
   -webkit-transform: perspective(1000px);

But it seems not be needed anymore.

It seems Google fixed here some things... I am using Chrome Version 56.0.2924.87



When using the workaround now (!) the image looks blurry. When not using, the scaled images look better / crisper now.


But the jitter bug in IE (snapping to fixed pixels while scaling, not animating smooth) still persists.


Here i am using still the workaround

rotationZ: "0.01deg"

within the tween.

  • Like 1
Link to comment
Share on other sites

Thanks for reporting this Technics1210,


That would make sense since Google Chrome will break something, then you will have to do a fix with adding perspective. Then they will fix that previous thing they broke and you have to remove perspective. And then the previous fix will break the previous broken thing, and on and on and on. That is pretty standard with Google Chrome and has been happening since Chrome 21.


Reminds me of this topic that documents that weird perspective bug in Chrome.




So by your post its back to just triggering matrix3d() or translate3d to fix the blurriness. But chances are in either the next build of Chrome after this Chrome 56, that some new bug or old bug will rear its ugly head like 6 headed snake. And we will need to add perspective to fix the blurriness again.


Hail Hydra! :)

  • Like 4
Link to comment
Share on other sites

  • 3 weeks later...
  • 2 months later...

Yea, I'm seeing this again on Chrome 59.


This time I'm using <img> tags too!


This demo looks ridiculous at the moment:


See the Pen 39f1aa3a003e729d7dd4122beeee7c4c by GreenSock (@GreenSock) on CodePen


Despite what the last comment on this Chromium issue says:

https://bugs.chromium.org/p/chromium/issues/detail?id=596382&can=2&start=0&num=100&q=chrome 49&colspec=ID Pri M Stars ReleaseBlock Component Status Owner Summary OS Modified&groupby=&sort=



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.
  • Create New...