Jump to content


Popular Content

Showing content with the highest reputation on 05/24/2019 in all areas

  1. 2 points
    OSUBlake is right regarding setTimeout. Take a look at the last codepen i posted above and see if that might help. It's proving to be much more reliable.
  2. 2 points
    Using setTimeout will cause issues, especially if you leave the page and go do other work on your computer.
  3. 1 point
    Gotta be honest — I thought that sentence was gonna end with "we don't allow CSS animations around here." 🤣 Since Zach has a shiny new GreeenSock Admin badge, it's probably time to dust off the chalkboard.
  4. 1 point
    Hey waschbaer__ and welcome to the forums! I'm not sure exactly what type of effect you're looking to get, but you have an extra section at the top that is throwing off the timings in this demo. Removing it seems to fix the issue in the demo you provided: https://codepen.io/ZachSaucier/pen/vwdMwe?editors=1000 Besides that, I'd be careful nesting general selectors like you're doing (such as $('.textfade_Slide1').each()) inside of other general selectors. If you have anything with the class textfade_Slide1 in multiple sections you could face some weird issues. If you're reusing animations, it might be better to scope the selector by doing something like $(self).find('.textfade_Slide1').each(
  5. 1 point
    Anybody else see flickering? I seriously doubt this related to GSAP. Most likely a browser rendering issue. I bet you wouldn't see any problems using canvas. https://codepen.io/osublake/pen/vpEQzY
  6. 1 point
    Also, for the record, I'd recommend avoiding className tweens because those require looking at literally every...single...CSS property to find anything that has changed between the old and new className, and then tweens each one. It's much better to just specify the properties you want to animate. If all you're doing is swapping classes, it's probably simpler to just use a CSS transition. Oh, and there is one case where an image's src must get updated internally, and that's for backgroundPosition because it has to measure the width/height of the native image so that it can accurately handle things like percentages. As far as I know, it's impossible to do otherwise. I found the original email notification about this thread and it contained a link to a valid codepen, so I peeked at that and it does indeed look like you've got a backgroundPosition in play there, and it's percentage-based. Perhaps that explains things.
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up