geedix

The mouse event isn't getting through to the primary logo because the secondaryLogo is in the way. If you put the event listener on secondaryLogo, it works.

If you mean the mask is moving too slowly, then you could specify a shorter duration for your tweens, like gsap.to($middlemask, { x: e.clientX, y: e.clientY, duration:0.2 }); - it's just using the default 0.5 right now. But maybe that's not what you mean?

Hi Adel, I put your code into a pen: https://codepen.io/geedix/pen/yLKNNYW?editors=1111 I changed the timeline to repeat once, instead of using the 'restart' command. I think that will work better for playing your animation twice. good luck

I realize it's hard to help with a bug that I can't reproduce on Codepen, but allow me to talk to myself for a minute. I think FF is just chugging a bit. It's slow to turn the opacity on and off when swapping sprite sheets, in the context of a busy page. I can fix the problem by showing the new sprite .05 seconds sooner than I hide the old one. The problem is that you can glimpse the overlapping frame in other browsers. I'll keep working on it and report back if I find a solution. My ideas include forcing the GPU to get involved, changing the timescale, doubling the last frame in each 18-frame sprite... or detecting FF and skipping the animation for those users. Let me know if you have ideas, too. thanks

Well I made a Codepen, but I don't see the flicker here. Maybe this will help me figure it out... but it seems like it might take me a while to crack this one... https://codepen.io/geedix/pen/dyJRmbg

Maybe someone knows why my spritesheets animate fine in Chrome, Edge, Safari - but in Firefox they give a little blank flash when switching to the next spritesheet? I'm using GSAP with stepped ease to animate nine spritesheets, each with 18 frames, one after the other. They're 8192px wide and move horizontally by 442px per frame. If I slow the animation down to one frame per second, you can still see a blank flash on Firefox when going from one spritesheet to another. The flash is only for a brief few milliseconds. In my timeline, when one spritesheet's tween finishes, I set its autoAlpha to 0, and the next one to 1. This seems to be when the flash happens. I'll work on a Codepen example, and see whether it still happens there. thanks

I did banners for years using both gsap and Animate, but didn't often use them together. You don't want to try moving the same things with both at once -- they won't cooperate. The timeline in Animate is good for character animation, keyframe drawings and complex masking. Gsap is good for smooth easing, transitions and scripted effects. As Carl mentioned, Animate has its own library, CreateJS. You can do scripted animations using that, since it's already loaded in Animate. It's not as much fun as gsap though.

You could add a css rule to hide the text until javascript can reveal it, like this: https://codepen.io/geedix/pen/WNdezBW

Thanks. I thought javascript would follow instructions in sequence, meaning the timeline would run each tween and THEN run the seek command at the bottom. And I thought that declaring the timeline as a variable was the same thing as creating it. But I see now that I was mistaken.

I guess I don't understand "seek" because I just skipped all the prefers-reduced-motion stuff and I still can't get it to seek a label.

I have done something like this before with success, but tonight, I can't make my timeline skip ahead. It logs 'true' for me if I set my mac to prefer reduced motion, or do it in dev tools, but it won't "seek" a future time or label. What am I forgetting? thanks

Thanks, I appreciate the explanation and solutions.

I'm having trouble applying timeScale changes to a timeline. If I comment out the timeScale part, then the timeline replays, but with it in, it stops. thanks

Yes, you can have video under a mask or clipping path. I've done this in rich media banners. Ad networks can have their own video restrictions, such as requiring you to use their player, show their persistent controls and use their tracking.

The problem is that the DOM doesn't know about things inside a canvas tag. You have to go through extra steps to manage tab focus and get some of that functionality back. This article looks like it might help you - https://codepen.io/servinnissen/post/a-somewhat-accessible-canvas