StopLogic
Content Type
Profiles
Forums
Store
Blog
Product
Showcase
FAQ
Downloads
Everything posted by StopLogic
-
I promised that when I find a solution, I will write about it here. After a long search for the cause of the strange behavior of the blocks, it turned out that you just need to install the npm gsap module again. After reinstallation, everything worked as it should. Thank you again for your help! Gsap is like a Hogwarts diploma because it allows you to work magic!))
-
unfortunately, I cannot reproduce the problem in codepen, but I can link to my project so that you can see the error in this particular example. Can I send a link to you personally to keep your privacy?
-
Thanks for your fast answer, and sorry for my bad english! There is my codepen example: codepen example in my project, the double-pined-parent, every time the screen resolution is changed, goes down to its own height, leaving the pinspaser in its place. That is, if I change the resolution 10 times - a double-pined-parent with a height of 1000 pixels will go down by 10,000 pixels. If I completely remove the animation script for one of the blocks, the problem disappears
-
Hello! I got a problem: I created a block that is a trigger for two child blocks. When scrolling the page, the parent block is pinned first until the animation of the first child block ends, and then again until the animation of the second child block ends. In this situation, when the page is resized, the parent block moves down to its own height each time. How to properly organize this animation?
