The MDC docs are pretty clear:
Note: Gecko (Firefox) accepts a length value for tx and ty.
Safari (WebKit) and Opera currently support a unitless number for tx and ty.
After a lengthy post explaining the logic of the matrix, Brendan Kenny concludes that one must
"add units to e and f for
Firefox (which doesn’t really make any
sense, but for now: fine)."
Which is true - for the computer - as the linear translations are technically no different than the other entities of the matrix.
But it is unfair, as - for us humans - it makes logical sense for the linear translations to be in value amounts, and there is no other good way to get the browser to do percentage calculations.
Hopefully, the FF implementation will win.
As an aside, I have read, but not yet tested that the third and fourth values are input into Webkit in order, but in FF and IE in reverse. From the docs:
-moz-transform: matrix(a, c, b, d, tx, ty)
Where a, b, c, d build the transformation matrix and tx, ty are the translate values.
┌ ┐
│ a b │
│ c d │
└ ┘