Re:CSS Triggers
by onion2k on Monday July 28, 2014 @07:19AM
(#8096092)
What the site fails to explain is why these things are important. Changing a property that effects a layout change means the browser will need to redraw that element and anything that the geometry has pushed around. A full repaint is slow so if you're doing it often the user's experience will be very negatively impacted. A composite event should be pretty fast as it happens largely on the GPU hardware.
For this reason, for example, animating things with a CSS transform is considerably better for the user than animating a property like left or margin-left. Animating with CSS can be much better than something like jQuery's animate().
If you want to know more, google 'layout thrashing'.
Re:CSS Triggers
by zevyoura on Monday July 28, 2014 @05:43PM
(#8099511)
If you click on a property name, it actually gives a pretty decent explanation. I agree a link to additional overall context could be useful, but I think you're overstating the gap.
For this reason, for example, animating things with a CSS transform is considerably better for the user than animating a property like left or margin-left. Animating with CSS can be much better than something like jQuery's animate().
If you want to know more, google 'layout thrashing'.