cwiens

That is a big factor too, those ad spaces, right and left columns on sites have become blind spots. They have been around for decades now and folks know to ignore them. RDA's although often less attractive appear in unexpected places. Social is video if you want motion so that is huge factor too. Maybe page takeovers? Not sure.

Although I am using Greensock in other ways, almost 100% of my ad requests are RDA and video these days. They have a much higher CTR. I miss making HTML5 GDN ads, telling little stories in a few seconds, maybe it is just the companies I have been working for? Curious if you'all have been experiencing the same.

Just tried it today. It made some weird choices but it shows some promise for sure.

https://greensock.com/docs/v3/GSAP The video here about half way through has some audio overlapping.

I was thinking that too. Thanks for jumping in with your expertise!

Found the solution. Not completely sure why putting it in a function solved it but this created zero errors. var item = $('[aria-label="myElement"] svg') go(); function go() { TweenLite.to(item, 1, {left:"63px"}); }

I was just trying to un-minify the app.min.js file to see where the heck that error is pointing to. It is hard to get through to someone technical enough on the Storyline end to understand questions like that.

Storyline does not give me any control over publishing min files.

I took that out and it no longer throws the above error. Still the push errors though.

Sorry about that. Put the wrong link. This is pointing to an uncompressed TweenMax.js file. https://360.articulate.com/review/content/2c72465e-38f4-44ec-9b5a-e0295c4a6601/review

It works well so I am tempted to just ignore the error. I use GreenSock outside of Storyline all the time and would love to get it working in our eLearning authoring tool, Storyline. The animation tools are weak in Storyline.

Here is the most simplified I can get it. There are just two triggers (storyline coding) that first load the CDN and then tween the box on the stage. You can see for all 3 tweens it throws the PUSH error. https://360.articulate.com/review/content/e71d0732-f5d1-4f16-817f-c7c3a2c5be3d/review var bx = $('[aria-label="box01"] svg') TweenMax.set(bx, {transformPerspective:450}); TweenMax.to(bx, 4, {alpha:1, scale:.8, rotationY:45, ease:Back.easeOut}); TweenMax.to(bx, 4, {delay:4, scale:1, rotationY:-45, ease:Back.easeOut}); TweenMax.to(bx, 4, {delay:4, scale:5, rotationY:0, ease:Back.easeOut});

Thanks for the reply. Yes, I agree, Storyline is making it difficult for sure. Since it is a push error I was wondering if Greensock was tripping on the [] in the variable definition. I will try to strip it down further and point to the uncompressed TweenMax.

Sorry I am not able to create a CodePen for this because it is happening in storyline. I figured out how to use Greensock directly in Storyline by using this code to get the object name using Jquery. var SL1_01 = $('[aria-label="leftIntro"] svg') TweenMax.set(SL1_01, {transformPerspective:450}); TweenMax.to(SL1_01, 4, {alpha:1, scale:.8, rotationY:45, ease:Back.easeOut}); Here is an example in Articulate Review, after you click start the left stripes rotate. https://360.articulate.com/review/content/28f18475-4a3c-4eef-ba4e-37546b6d5c20/review For every tween it throws an error, but still works perfectly. Uncaught TypeError: Cannot read property 'push' of undefined at g.l.render (TweenMax.min.js:14) at Object.o.render (app.min.js:3) at Object._._updateRoot (app.min.js:3) at Object.o.dispatchEvent (app.min.js:3) at e (app.min.js:3) Is it because of the brackets? It does not work without them. The only way to target objects in Storyline is to use the Accessibility feature and name object and include the svg statement at the end. Again this works great but throws the above error with every object we tween. I would love to just ignore the error but would rather solve it :). Thanks for