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

Re: [CSS-transforms] rotate(<angle>[, <translation-value>, <translation-value>])

From: Dirk Schulze <dschulze@adobe.com>
Date: Thu, 16 Feb 2012 09:25:36 -0800
To: Chris Marrin <cmarrin@apple.com>
CC: Rik Cabanier <cabanier@gmail.com>, "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
Message-ID: <22CE4C57-D627-49E9-A353-5EB7FC2654DE@adobe.com>
Both is correct. We have the spec text:
"The computed value of the transform property is a matrix() or matrix3d() value that describes the matrix that results from concatenating the individual transform functions"

and the issue 6:
"We need to resolve whether the computed value is the same as the specified value, or matrix()."

I would be happy if that changes. But should be another threat.

Dirk

On Feb 16, 2012, at 9:20 AM, Chris Marrin wrote:


On Feb 15, 2012, at 1:25 PM, Dirk Schulze wrote:

Hi Rik,

see inline comments:

On Feb 15, 2012, at 1:09 PM, Rik Cabanier wrote:

Hi Dirk,

just to make it clear to me. The issue you are trying to resolve is if you have content that is like:
<HTML>
...
<svg>
...
<g id='id' transform="rotate(45, 10, 10)">

and you call:
getcomputedStyle(document.getElementById("id")).transform

it should return:
"rotate(45deg, 10px, 10px)"

With the current specification it would return a matrix. Like for every function. This is also implemented by all browser that way. But for SVG DOM you would get a rotate as transformation function, yes.

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.

-----
~Chris
cmarrin@apple.com<mailto:cmarrin@apple.com>
Received on Thursday, 16 February 2012 17:26:11 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:50 GMT