PointC Posted February 27, 2020 Share Posted February 27, 2020 Hey all, Just a FYI here. I'm working on a new project with Pixi and CustomEase/Wiggle and started getting weird errors and missing sprites. A look at the console showed DevTools failed to parse SourceMap: ... (followed by some GSAP map files). This seems like a new bug and has been reported. https://bugs.chromium.org/p/chromium/issues/detail?id=1052872 Just thought I'd post in case anyone else was experiencing some issues. Happy tweening. 2 Link to comment Share on other sites More sharing options...
ZachSaucier Posted February 27, 2020 Share Posted February 27, 2020 That may explain the reason why we were having the same issue with ScrollMagic: 1 Link to comment Share on other sites More sharing options...
PointC Posted February 27, 2020 Author Share Posted February 27, 2020 Ha. I just saw that thread right after I posted. That'll teach me to be on hiatus. Uploading the GSAP map files seems to help, but my ad blocker source files occasionally fail to parse too so that can mess things up. I guess it all depends on what extensions you have and how badly you need them. Development sure is fun. 2 Link to comment Share on other sites More sharing options...
GreenSock Posted February 28, 2020 Share Posted February 28, 2020 Yeah, I've been seeing that a lot lately myself. In 3.2.2 (just released), I removed the references to the sourcemap files so that should eliminate some of the confusion. I'll probably add them back in a while after Chrome addresses the issue. Seems pretty clear it's a bug on their end. And frankly I'm not sure how many people are even using the GSAP sourcemap files anyway. 1 Link to comment Share on other sites More sharing options...
PointC Posted February 28, 2020 Author Share Posted February 28, 2020 Chrome sure loves to introduce bugs. Perhaps it's time for a GreenSock browser? 2 Link to comment Share on other sites More sharing options...
OSUblake Posted February 29, 2020 Share Posted February 29, 2020 On 2/27/2020 at 1:42 PM, PointC said: That'll teach me to be on hiatus. So are you done with your hiatus? 2 2 Link to comment Share on other sites More sharing options...
PointC Posted February 29, 2020 Author Share Posted February 29, 2020 7 hours ago, OSUblake said: So are you done with your hiatus? I could probably pop in a little bit, but @ZachSaucier seems to drop a first answer on most threads in a few minutes after posting and then you, @Shrug ¯\_(ツ)_/¯ and @mikel clean it all up. It looks like there's nothing left for me. I'll probably just put myself out to pasture as I no longer have the energy for answer battles. 👴 Link to comment Share on other sites More sharing options...
ZachSaucier Posted February 29, 2020 Share Posted February 29, 2020 3 minutes ago, PointC said: @ZachSaucier seems to drop a first answer on most threads in a few minutes after posting You used to do the same thing to me 😄 4 minutes ago, PointC said: then you, @Shrug ¯\_(ツ)_/¯ and @mikel clean it all up Yay for helping cleaning things up \o/ Link to comment Share on other sites More sharing options...
Shrug ¯\_(ツ)_/¯ Posted February 29, 2020 Share Posted February 29, 2020 20 minutes ago, PointC said: no longer have the energy for answer battles. Your glory days are still something to behold though. Look at those green socks and impressive skills vs that massive SVG entity. @PointC, come on champ we need you back on the forums !!! 2 Link to comment Share on other sites More sharing options...
infrared Posted April 9, 2020 Share Posted April 9, 2020 I'm so confused how to fix this? i am using gsap within Google Web Designer. I am seeing the issue of gsap not loading and throwing this error not only in published files in chrome, but also in the GWD staging in firefox. I am very worried someone else will open a link and get this mess, but so far no one but me has encountered it. I am using <script src="https://cdnjs.cloudflare.com/ajax/libs/gsap/3.2.4/gsap.min.js"></script> any advice would be SOOOO appreciated. Link to comment Share on other sites More sharing options...
GreenSock Posted April 9, 2020 Share Posted April 9, 2020 Hi @infrared. Are you saying that you see a message about Chrome having trouble parsing a sourceMap file? I can't imagine that's the case because the file you linked to doesn't even reference a sourceMap. Could you give us more details about the problem you're encountering and how we can see it too? We'd love to help, but I just don't understand what you're asking. 1 Link to comment Share on other sites More sharing options...
infrared Posted April 10, 2020 Share Posted April 10, 2020 I keep encountering this message: DevTools failed to parse SourceMap: and links to https://s0.2mdn.net/ads/studio/cached_libs/gsap.min.js.map I have also consulted tech support at google web designer google chrome Version 80.0.3987.163 (Official Build) (64-bit) this is how i am linking greensock: <script src="https://cdnjs.cloudflare.com/ajax/libs/gsap/3.2.4/gsap.min.js"></script> maybe it is something particular to my mac? like a dns issue? i would share my source file but the content is for an ad not launched yet thanks for any advice steve Link to comment Share on other sites More sharing options...
PointC Posted April 10, 2020 Author Share Posted April 10, 2020 Did you try 3.2.6? I seem to remember @GreenSock mentioned stripping out the reference to the map file. I'm not sure what version that was though. 2 Link to comment Share on other sites More sharing options...
PointC Posted April 10, 2020 Author Share Posted April 10, 2020 Correction. That info was in this very thread. Duh. I must be tired from quarantine. Seems that was removed in 3.2.2 so that is weird. I'm not sure. I think @GreenSock will need to jump into this one. Link to comment Share on other sites More sharing options...
GreenSock Posted April 11, 2020 Share Posted April 11, 2020 First of all, this is a Chrome bug and has nothing to do with GSAP. It affects all libraries that point to source maps, and it'd only show up if you have Dev Tools open. Second, we removed the pointer to source maps a while back and the version you said you were pointing to has no such reference (look at the bottom of the code yourself). So there MUST be some other version loading on the page that you're talking about. Do you have a link to the page you're seeing that error on? It doesn't even have to be your real project (in fact, it's better if it's not - we only need the most reduced test case possible). 2 Link to comment Share on other sites More sharing options...
infrared Posted April 11, 2020 Share Posted April 11, 2020 I got a message from google web designer tech support that they are working on resolving this issue and hoping to push out an update tues or wed. Crossing fingers this will take care of the issue. thanks for your help! 1 Link to comment Share on other sites More sharing options...
bigmamainthemud Posted July 7, 2020 Share Posted July 7, 2020 Just want to chime in here. I have the same problem and it's not breaking my code but I like a clean console. Just wanted to tag along until there's some answer. Thanks! B Link to comment Share on other sites More sharing options...
ZachSaucier Posted July 7, 2020 Share Posted July 7, 2020 @bigmamainthemud Are you using the latest version of GSAP? It shouldn't be occurring any longer... If it is please share a minimal demo of your situation. 1 Link to comment Share on other sites More sharing options...
bigmamainthemud Posted July 7, 2020 Share Posted July 7, 2020 Yeah it's the latest 3.4.4 from this link: 'https://cdnjs.cloudflare.com/ajax/libs/gsap/3.3.4/gsap.min.js' Here's the site I'm getting that error: https://mediagarbage.com/new_site/#home Thanks Link to comment Share on other sites More sharing options...
ZachSaucier Posted July 7, 2020 Share Posted July 7, 2020 1 minute ago, bigmamainthemud said: Here's the site I'm getting that error: https://mediagarbage.com/new_site/#home You're using old versions of the TextPlugin and ScrollToPlugin. Upgrade those to the latest versions and the warning will go away. Also might fix the warnings about null targets 1 Link to comment Share on other sites More sharing options...
bigmamainthemud Posted July 7, 2020 Share Posted July 7, 2020 Just realized the null targets were me poorly rewriting things and forgetting old vars so totally on me. Thanks for letting me know about the oldness factor. I'll get all the newness in their now. Gracias amigo! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now