Re: [CSS-transforms] rotate(<angle>[, <translation-value>, <translation-value>]) from Aryeh Gregor on 2012-02-16 (www-style@w3.org from February 2012)

From: Aryeh Gregor <ayg@aryeh.name>
Date: Thu, 16 Feb 2012 13:13:06 -0500
To: Chris Marrin <cmarrin@apple.com>
Cc: Dirk Schulze <dschulze@adobe.com>, Rik Cabanier <cabanier@gmail.com>, "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
Message-ID: <CAKA+Ax=DFFPcJKrD8C19eZcsnUbDSgQf4_x5ZS=Kh2OUBHRNbA@mail.gmail.com>

On Thu, Feb 16, 2012 at 12:20 PM, Chris Marrin <cmarrin@apple.com> wrote:
> But I don't think the spec requires a matrix, does it? We have an open bug
> in WebKit to do a better job of returning the original sequence of transform
> functions when possible.

getComputedStyle() returns a string of the form "matrix(...)" or
"matrix3d(...)" in all cases.  Very possibly this isn't desirable,
since it means resolved and computed values are different.  But it's
what all browsers do, quite interoperably.  (IE10 seems a bit
aggressive in returning matrix3d(), and Firefox until just a few days
ago added "px" where it shouldn't have, but that's about it.)  Is
anyone really interested in changing behavior when we already have
*four* independent interoperable implementations?

Received on Thursday, 16 February 2012 18:13:56 UTC