You need to
before you can comment on or make changes to this bug.
When transitioning between two transform:translate() values, the transition only works correctly if both pre- and post-transition translate states use the same length units.
* In WebKit Version 5.0.3 (6533.19.4, r78685) & Safari Version 5.0.3 (6533.19.4) when the transform:translate() units differ and the transition is stopped before completing, the transition jumps to the end translate state before reverting at a higher speed to finish at the correct time
* In Chrome 9.0.597.102 (and Opera 11.01) if transform:translate() length units differ (initial = px, :hover = %), then the change is instant and the transition is ignored.
* Firefox 4 beta 8 gets a gold star for rendering as expected
Created an attachment (id=82830) [details]
I see different behavior with and without accelerated compositing enabled.
(In reply to comment #2)
> I see different behavior with and without accelerated compositing enabled.
Actually that's not true. This is related to interrupted transitions.
This is expected for now. We don't have the smarts to convert both endpoints to the same units before transitioning.
*** This bug has been marked as a duplicate of bug 23775 ***