Jump to content
GreenSock

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

Shaun Gorneau last won the day on March 3 2019

Shaun Gorneau had the most liked content!

Shaun Gorneau

Moderators
  • Content Count

    688
  • Joined

  • Last visited

  • Days Won

    21

Shaun Gorneau last won the day on March 3 2019

Shaun Gorneau had the most liked content!

Community Reputation

1,596 Superhero

About Shaun Gorneau

  • Rank
    Advanced Member
  • Birthday May 31

Contact Methods

Profile Information

  • Gender
    Male
  • Location
    Hartford, CT

Recent Profile Visitors

6,032 profile views
  1. Ah, sorry @ZachSaucier! I had just started to reply when I got pulled away from my desk. I should know to back out fully when that happens! 🤦‍♂️
  2. I'm not on a retina display ... an older 2015 iMac
  3. A few notes on GSAP 3 syntax. Duration is now a property within the vars object ... and a timeline can have default property values! Because all of your tweens have a 1 second duration set, rather than set them on each tween, you can set them in the defaults. The same is true for rotation and ease! Of course, where ever you would like some other value, you would just include those on the tween. Have a look here, https://codepen.io/sgorneau/pen/OJPrjVg?editors=1010
  4. Looking at this in Firefox 72.0.1, I really don't see any remarkable glitch or jank (that I don't also see in Safari or Chrome, that is). Although, using string percentage values for the x/y properties could be contributing to that. Try using xPercent and yPercent as they take numeric values. https://codepen.io/sgorneau/pen/KKwbqOR
  5. @Richdigdesign I'm not even sure you need split text for this. To me it just looks like a series of animated lines, each with a "home" position and (eventually) highlighted text. Something like this, https://codepen.io/sgorneau/pen/oNgQmGd Of course you'll want to adjust your final "landing" spot for each segment. And you'll want to look at how these lines of text are created from a semantic and accessibility standpoint. Hope this helps! Shaun
  6. As a start, seeing your site on mobile could reveal some big/obvious issues ... so certainly post the URL
  7. If I understand correctly, you'd like to tween "visibility". But, visibility isn't a tweenable property because either it is (visible) or it isn't (hidden), there are no states in between. Taking a step back, what is it you're trying to achieve that leads you to believe visibility: hidden; is the answer?
  8. Hi @Gilbert, For a dynamic value you’ll want to do something like
  9. Hi @Zahir Rafiq The problem is in each of your click events, you're only accounting for one other color's timeline to have been played when either of the two other colors' timeline could have a progress greater than 0. For example, your green click event only looks to see if the red timeline has a progress value ... it doesn't check if blue does. Have a look at this codepen to see how I've addressed that. Now ... this works well for a few colors. If we were allowing for this on something like 10 colors ... of course this way would quickly get out of control and we would want to abstract that away somehow. https://codepen.io/sgorneau/pen/MWYGXaq?editors=0010 Happy tweening! Shaun
  10. Ah, it was so subtle I missed it! I see what you're talking about now. It's all about the transform origin and the type of transform (moving along the x and y axes). All of the petals are still in their basic "box" position and the ones that "stand out" are transforming in a direction that is visually unappealing. All transforms are happening, just in a way that "relatively" doesn't look right. Instead, maybe look at transform: rotate() for the petals and tweening those from a relative rotation. Something like this, https://codepen.io/sgorneau/pen/bGNvxoq Hope this helps!
  11. What browser are you seeing this issue? In Safari, I see no issue whatsoever.
  12. I'm not sure of what kind of effect you're going for here, but maybe this can help. https://codepen.io/sgorneau/pen/bGNLyLO
  13. You’re welcome, @eomerb!
×