Jump to content
GreenSock

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

NubieHere

ShockinglyGreen
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

7 Newbie

About NubieHere

  • Rank
    Advanced Member

Recent Profile Visitors

810 profile views
  1. Unfortunately not. It was the simple fact that I hadn’t wrapped the string for the background-image property in url() ... the code was part of a way to complex example to simply pull out. I’ll see if I can find the time to recreate a snippet just to see if that’s redoable. Thanks.
  2. OK, wild guessing here made me find the answer ... I had a backgroud-image set directly with an url. BUT I left out the url() wrapper on the string ... and then I guess gsap somehow renders it invalid (or whatever) and removes it. Que?
  3. Hi, I see that gsap overrides the already applied styles set on the element through markup ( '<div style="yadda yadda"' ... gets overridden ) ... how do I avoid that, and simply have gsap add the properties it needs to work? I set a background-image on the element using the style attribute ... and when doing a gsap.to() ... it removes the background-image element from the style ... that's NOT what I would expect.
  4. OK, the problem seemed to be that I didn't know you could pass in a jQuery object as the target ... fixed the issue.
  5. I need to somehow reset a timeline and reapply it in a safe and robust way. As you can see in the codepen the close button (the black circle with a white cross in the upper right corner when clicking one of the colored boxes) the cross rotates just fine the first time, and then – depending on when you click to close it – it starts to get weird. Next time you click a colored box, the cross start off from the same position when you clicked to close it. Somehow makes sense I guess as the rotation is somehow at that point in time. But it also doesn't fire at all at random ... so, how can I make SU
  6. Thanks for clearing that out Carl. Lesson learned: whenever GSAP 'misbehave', check your own CSS ; )
  7. Hi, Why is this (see codepen) first animating the element to the top and the left, and THEN animating the width and height!? I would EXPECT it to animate ALL properties at the same time ... as I guess any user would. So, WHY is it behaving as it does, and what would be the argument that it indeed should behave like this? It seems counter intuitive ... at best.
  8. But adding the 'false' now breaks preload progress ... so all in all this preload.js is a big pile of pooh. You fixed one problem only to have created another one ... it seems endless …
  9. Yeah, you were right. It turned out to be: new createjs.LoadQueue( false ) missing the 'false' ... Even though I did try both true and false, and even the default (none). And when I type 'gsap' into the javascript resource in codepen ... i get this (see image) ... and that's not gsap 3.0 if I'm not mistaken?
  10. No, I cannot provide a codepen, as the code is overly complex. But basically I have the issue of when using gsap to fade in an initially opacity 0 element with a background-image set the image just wacks on somewhere randomly in the transition. BUT when I use css transition: all 1s ease-in ... it works fine. Now, does anyone have ANY experience with (some buggy browser catch) using fade in and fade out of elements with background-image set while the image is faded out (opacity: 0) and then fading in? Basically what I do is: fade OUT an element with a background-image se
  11. Thanks. I was suspicious of that ... and did exactly that just to be sure.
  12. Yes, I know my tween wasn't correct ... I was just thrown off into the realm of getting this to work in the first place – one problem at a time you know. I've fixed that now, and it's working 'as expected' ... thanks again for pointing this stuff out. All I wanted was an isolated example of how SplitText would behave if I set the text of an empty element in code prior to tweening it. Would it flash briefly before hiding it and then fading it in ... I guess the result is: no, it perfectly hides it. Which is nice. Simple stuff like this often turn into to some hackish nightmare as the creator of
  13. Great, didn't have the console open ... why would I on codepen ... would expect IT to tell me that I had an error (some kind of indication that my markup, styling or code was failing ... ). Guess I just had to learn that about codepen the hard way. Thanks.
  14. OK, someone please tell me why it turns in to a bleedin' nightmare creating a simple codepen for testing SplitText with an initially empty element? What is it that I'm CONSTANTLY missing about this library!? I've added these resources: https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js https://cdn.jsdelivr.net/npm/gsap@3.0.1/dist/gsap.min.js https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/SplitText.min.js
  15. Great, exactly. I'm still wrapping my head around using this thing properly ...
×