Webkit translate3d issues (peek-thru)?

Solution! After a night of sleep, I mulled over the culprit and what to do with it. It's not necessarily the act of animating a child element with translate3d but rather the face that the element that was translated has that CSS property at the time it's parent is being animated with translate3d.

Solution! After a night of sleep, I mulled over the culprit and what to do with it. It's not necessarily the act of animating a child element with translate3d but rather the face that the element that was translated has that CSS property at the time it's parent is being animated with translate3d.

The fix is to first animate the child element, then remove the translate style all together. The CSS structure is now: /* default class for the start of your element */ . Modal-startposition { -webkit-transition-duration: 1s; -webkit-transform: translate3d(0,-618px,0); } /* add this class via jQuery to then allow webkit to animate the element into position */ .

Modal-animateposition { -webkit-transform: translate3d(0,80px,0); } /* when animation is done, remove the above class and replace it with this */ . Modal-endposition { top: 80px; } And some sample jQuery: //attach a click event to trigger and then... $myModal . AddClass("modal-animateposition") .

One('webkitTransitionEnd',function () { $myModal . RemoveClass('modal-startposition') . RemoveClass('modal-animateposition') .

AddClass('modal-endposition'); }); A little tedious, but it completely fixes the screen redrawing problem.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.