Jump to content
GreenSock

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

Fivetwelve

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

2 Newbie

About Fivetwelve

  • Rank
    Newbie

Recent Profile Visitors

1,013 profile views
  1. Hey, @danboyle8637, thanks for the follow-up. I eventually saw your approach in the Gatsby debugging section. I, too, am using Netlify so I'm very pleased to hear it's working great for you. I will try that as well. I do hope that we'll be able to get a point where this exception is not necessary. I think GSAP and React are both amazing frameworks. There's much better integration than when I first tried using them together a few years ago.
  2. Hi, Jack— I'm not an expert on server-side rendering but the crux is anytime a module is looking for document or window property, it will fail because those browser properties aren't available. A Gatsby doc discusses workarounds from the dev perspective but not actual solutions for the module creator: https://www.gatsbyjs.org/docs/debugging-html-builds/. Honestly, the best way may be to reach to some other folks who may have dealt with this. Here's an example. On my project, I've had to add an image/slide carousel (I know, don't get me started...). I know there are a fa
  3. I encountered the same error with the DrawSVGPlugin since I also had to import the file locally. I see the same error whether I used the typical or UMD version of the plugin. I, too, am using Gatsby. As mentioned earlier Gatsby's build script generates an isomorphic version hence the errors while it works fine for local dev builds. I'm not sure how @danboyle8637 managed to suppress the warning but I didn't feel comfortable attempting that in the event it fails in my build pipeline. I opted to move the import into gatsby-browser.js and it worked that way. Any imports the
  4. I eventually managed to work around this. Although the elements tweened properly the first time, the second time around required that the direct parent's visibilty be adjusted. My elements tweened in TimelineLite were the children of a container but not the direct descendants. i.e. I had #section0 > .someContainer > h2 I added TweenMax.to($('#section0 .someContainer'), 0, {autoAlpha: 0, overwrite:'all'}); to the beginning of my toggle back to the first tab and it worked. It seems that when the child elements completed their tween the parent's visibility:hidden kicked in. And d
  5. Hi, there— I'm hoping someone can help suss out what I'm doing wrong. I have a page that has 2 blocks of content with a couple of <li> elements to toggle between the two, like tabs. I'm using TimelineLite to show the first block, and—when toggling to the other block—TweenMax to hide the first block's elements and TimelineLite to transition in the second block's. What happens is page loads, first block appears. Toggle to 2nd block. 1st block is hidden, 2nd block appears. When I toggle back, 2nd block is hidden, 1st block appears BUT proceeds to disappear; it doesn't stay visible.
×