Jump to content

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


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Newbie

About massic80

  • Rank
  • Birthday 07/04/1980

Contact Methods

Profile Information

  • Gender
  • Location
    Collegno or Dogana Nuova, Italy
  1. Thanks for the answer There is no particular trigger for this question: I was just figuring out the complexity of your code, the several browser-exceptions you were applying, the difficulties of any amend by keeping in mind any legacy browser; all of this, above all, while keeping the first place in performance leaderboard Trimming IE8 (and IE6, as far as I can read on Draggable docs!) would save bytes, time, CPU cycles and above all neurons
  2. Hi all, I was wondering whether GSAP will drop support for legacy browsers. I never dug into its source code, but since it's compatible with ancient browsers, I figure out there is margin for optimizing it even more by dropping the support for them. I was thinking of something like jQuery did: a version for older browsers, another one for the latest (I know it would be harder to maintain). You probably already considered the possibility to drop them and you also probably already optimized the code in order to trim away whatever is not needed for current browser on landing i
  3. Thanks, I'll check it out I just can't find the release notes
  4. Sorry, Jack, I (we?) didn't fully understand your post.
  5. Thanks anyway, Rodrigo I thought you were the developer who submitted the latest changes Let's stay tuned on this topic, anyway. Massi
  6. Thanks a lot, Rodrigo. In fact, I don't care about YT code error, it's just a side effect from the example I chose I think that "odd" is a good definition for this weird problem: it becomes even more weird, because you just said that switching to minified version you didn't detect any error: I started from the minifed version (of course) and chose to use the uncompressed one on the example for a better view on the trouble origin (In the minified version, the error occurs on line 16). Did you leave the ten second timeout pass? Oh, right, what a surprise, having a problem on IE! Let's go
  7. Hi all! I set up a site using TweenMax 1.9.5 for any animation, and everything worked properly. Later, I updated the libraries to 1.9.7 and finally to 1.9.8. With current version, the animations don't work properly; there is a conflict with Addthis dynamically created iframes. Here is a sample code reproducing the problem with a YouTube static iframe: <!DOCTYPE html> <html> <head> <!-- 1.9.6 --> <!-- <script type="text/javascript" src="https://raw.github.com/greensock/GreenSock-JS/f91853a0e9f753c1ae8b6b36172a4d42759296af/src/uncompressed/TweenMax.js">
  8. Hi again, sorry for the delay, but I got fever. I think this is a good solution for keeping a "short event" synchronized with TweenMax ticker... but let me understand: is onComplete() event triggered when last "frame" is started? And... how could a setTimeout be synchronized as well? <!DOCTYPE html> <html> <head> <meta charset="utf-8"> <title>Insert title here</title> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> <script src="http://cdnjs.cloudflare.com/ajax/libs/gsap/1.9.4/TweenMax
  9. Hi again! I cant find out why, but it looks like WORKING! In my example, the timestamp at penultimate tick was around 50 ms before the last one, and the position was exactly the same (this may be due to a fraction of pixel for last tick), hence I didn't expect it to work with a delay of 1 ms. I was thinking of trying with isTweening() method or ticker property, but since you found an apparently working solution, I'll try applying it to my site and testing it deeply Thanks again, I'll let you know... there is a beer for you, in case you plan to pass around here Massi P.S.: maybe it's best
  10. At the moment I can't try, I'll let you know tonight (Italy time)... thanks in advance!
  11. Thanks a lot for your reply Jack, looks like I'm a scroll pioneer! Of course, when I said "turns out that it's TweenMax itself", I meant "it's only due to TweenMax animation, not other JS code around the page" Did you try my test code? Of course, if yours is a correct theory, there is nothing to do on library side... let's study this up (it's annoying)!
  12. Hi all! Today I was trying to execute some instructions on manual scroll event, avoiding the scroll animation performed by TweenMax. I attempted to initialize a boolean variable, which is false during the TweenMax animation and is restored to true "onComplete". On $(window).on("scroll") I checked the status of the variable. I found out that a scroll even was triggered even when my status variable was already returned to true: after some tests, it turns out that it's TweenMax itself. I tried on an empty page, reporting the following code in Firebug console, and looks like after the "hi" report