Rojan

Thanks for your answer Carl.

Hi Carl, It's me again. I have been coding an animation using GSAP recently and I came across a case that works fine in Chrome and Firefox but act strangely in IE including IE11. I eventually found a workaround but I thought maybe it would be something that the GSAP team want to take a look into. The problem appears when we have a <div /> with "height:XXpx" and "padding:XXpx 0" and we only want to animate this <div />'s padding to a different size. The truth is that the height doesn't change in the animation at all but... The problem: If we provide only the target padding, all the browsers including IE act normally with correct animation, but as soon as we also provide the target height which is practically the same as the initial height, IE animation gets ruined (other browsers still work correctly). When one inspect the elements, it can be seen that the height is being decreased during the animation in IE and comes back to normal at the end. Workaround: Not to include the height in the parameters, but this only works if we don't want to change the height during the animation. *) One thing that might or might not be the reason is that I have used a <svg /> element directly inside the <div /> which is being animated. Thanks for your attention in advance.

Well, that is awesome. It is so beautifully structured. And thanks for the super fast reply. You people rock. Keep the great work going.

Thank you so much for your replies Carl and PointC, I had newer thought that I hadn't gotten the timing positions in GSAP tools. With the comments from Carl and the suggestion from PointC, now I have understood the timing positioning better and gotten the code working as expected. Here is the updated demo for anyone curious about how I wanted it to look like: http://codepen.io/Sojaner/pen/eZyRzQ?editors=0010

Hi everyone, This is my first post here. First I want to say thank you to the people who provided these absolutely amazing animating tools for web which make the web a more fun place to code for. Then I think I have found a bug in the animation flow which at least exists in TimelineMax but I am suspecting the source to be in the TweenLite as to my understanding is the origin for all the animations. The problem: When I make a TimelineMax object and add TweenMax.to() animations to it, if the animation is done only on standard HTML elements things will work flawlessly, but as it can also be seen in the CodePen I provided, when I have a SVG element with its children elements, if I want to animate the children elements in the middle of a timeline two things will happen. 1) The SVG elements animation order will be missed up and will not work correctly. 2) The animation on the standard HTML elements will not wait for the SVG elements animation to be finished. In other words, the animation on the standard HTML elements registered after the SVG elements will be started on the same time as the first SVG element's animation. I have reviewed the order and timings several times and I think they are correct. I have also written the code several times from scratch to make sure that I am not messing anything up. It would be really nice if you can figure this bug out and release a new bug-fix version. I am currently working on a project and I really need this feature to word correctly. Thanks in advance.