Webkit seems to have a nasty bug that causes MAJOR slowdowns if you merely read a property from the calculated style after setting an inline value on a completely different element altogether, even of the property doesn't affect document flow at all (
WebkitTransform in this case). It forces a style recalc but it really shouldn't. Or am I missing something?
When you click "run test" below, we'll loop through all the letters,
getCalculatedStyle() on each one, and then set the
style.WebkitTransform to a random offset. Watch how much longer it takes if you select "Read transform before setting"! I know it'll go faster if all of the reading happens first, and then all of the setting, but that shouldn't be necessary.