Description
Whenever both a tweenCSS3 and morphCSS3 property is applied to an element, and both a tween and a morph sequence is started simultaneously (one immediately after the other), the one started later with the method start() will take precedence and the effect of the other will be completely ignored. For example, when there is a tween effect changing opacity from 0 to 1, and a morph effect manipulating top, left, height and width properties, and the tween effect is started later, the top, left, height and width properties will not be animated at all. As far as I could see, this is because both rely on CSS transition-property, and there is a race condition between the two animation sequences that run. This phenomenon does not arise with standard MooTools properties tween and morph, which happily carries out both animations.