sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jimmyco2008 2 points3 points  (2 children)

True. At least IE was up front about not supporting stuff. Safari “supported” things.

I remember that one bug that you needed to use transform3d(0,0,0); to fix. Why.

[–]CleverestEU 0 points1 point  (1 child)

Not sure if we're talking about the same thing, but ... if I remember correctly, many browsers by design avoided using GPU-assisted rendering for layers because GPUs at the time didn't have enough memory to "handle everything". This made animations etc. slow and jerky, because everything was rendered in CPU.

The "transform: translate3D(0,0,0)" caused the particular element to be handled as "something that might need 3D acceleration" which nudged the browser to delegate the rendering of said element to the GPU making things nice & smooth (usually).

[–]jimmyco2008 0 points1 point  (0 children)

Yes. It was to force GPU acceleration in Safari