Jump to content
GreenSock

Search In
  • More options...
Find results that contain...
Find results in...
cezaleo

chrome/firefox issue

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

If you view the codepen, I'm seeing completely different behavior across chrome and firefox.

 

Specifically in chrome, the last portion of the image is coming in all out of wack.

But in firefox it's better.

 

Is there something I could do myself to avoid this?

See the Pen Cjukm by ccelestine (@ccelestine) on CodePen

Link to comment
Share on other sites

Thanks for providing the demo (the effects are very nice), I occasionally see the last item animate in slightly differently.

For something like this however there is so much going on with so many random values that it is virtually impossible to know what is happening and why.

 

Instead of seeing a fully interactive slideshow of multiple images, it would be much easier to troubleshoot this if you provided a single Timeline animation that exhibits this behavior with non-random values and as few animated properties as possible to clearly show the variance. 

If you slap a scrubber onto the timeline then we can slowly move through the animation and perhaps get a better idea of what is happening.

 

By removing the non-random values we can also better compare how different browsers are handling the exact same animation.

 

You can grab some jQueryUI Slider TImeline Control code from here if you are so inclined: http://codepen.io/GreenSock/pen/Dtqwz

  • Like 1
Link to comment
Share on other sites

Hello, I was seeing something different.. Chrome animated fine and had the elements animating in from the center center (x y) of the viewport, whereas Firefox animated elements in from the bottom below the viewport.

 

I couldnt see the last part out of wack .. but a limited codepen like Carl advised would be helpful. :)

Link to comment
Share on other sites

Adjusted the css and now it's back to working.

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.
×