W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: [css3-transforms] translate() vs. translate3d()

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 10 Feb 2012 10:21:56 -0800
Message-ID: <CAAWBYDCAfSMvFMYB5AX+A+YChv3_bQ0v+sDi0v5kuiVHCprviA@mail.gmail.com>
To: Christoph Päper <christoph.paeper@crissov.de>
Cc: "www-style@w3.org CSS" <www-style@w3.org>
On Fri, Feb 10, 2012 at 3:15 AM, Christoph Päper
<christoph.paeper@crissov.de> wrote:
> Simon Fraser (2012-02-09 09:00):
>> <http://dev.w3.org/csswg/css3-transforms/#two-d-transform-functions>
> I haven’t cared about the transform (or animation) specs at all. I took a first look at the combined spec right now and I’m wondering:
> Why is it
>  rotate(α, tx, ty)   or   rotate(α)
> but
>  rotate3d(x, y, z, α)
> i.e. reversed order of angle and origin – or more generally: why are 3D functions not mere extensions of 2D functions with additional z parameters?

Argh, the commas, they kill me.

Please please please remove the comma between tx and ty, so rotate() a
two-arg function.  Then remove the commas between x, y, and z, so
rotate3d() is a three-arg function.

Received on Friday, 10 February 2012 18:22:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:11 UTC