Jump to content
Search Community

jel2013

Members
  • Posts

    4
  • Joined

  • Last visited

jel2013's Achievements

1

Reputation

  1. It's working perfectly with your new beta. I'm very impressed with your response time, and with the high level of continued support that GSAP is getting. It's obvious that I made an excellent decision to use GSAP.
  2. Ooops, I'm not sure the file got attached in my previous post. Here it is as a URL: http://192.210.192.144/GSAP-Bug.html
  3. I'm not using any plugins. It's quite a challenge for me to reduce my code to a small test case because of the way it's structured. But fortunately, I found some old test code from years ago that's only 1500 lines and exhibits the bug. It's attached.
  4. I am getting the following GSAP error on every version starting with 1.18.0. (Here, I'm using 1.19.0 uncompressed:) TypeError: end.match is not a function TweenMax.js:6888 and the stack trace is: _blobDif() TweenMax.js:6888 _addPropTween() TweenMax.js:6944 p._initProps() TweenMax.js:7272 p._init() TweenMax.js:7204 p.render() TweenMax.js:242 p.render() TimelineMax.js:313 p.render() TweenMax.js:6730 TweenLite.render() TweenMax.js:6992 p.dispatchEvent() TweenMax.js:6154 _tick() TweenMax.js:6206 (The error occurs in the minified version too.) I am using Firefox 49.0. Is anyone else getting this error? When I substitute any earlier versions (1.17.0 or less), GSAP works fine for me. I put in some tracing at the error point, and I found that the variable "end" is a boolean with a value of true. Of course, a boolean doesn't have a ".match" method, so that's the direct cause of the error. It looks like the "end" variable was first introduced in version 1.18.0.
×
×
  • Create New...