W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2012

Re: [css3-transforms] normalization of rotate3d() and computed values

From: Dirk Schulze <dschulze@adobe.com>
Date: Mon, 27 Aug 2012 22:24:47 -0700
To: "L. David Baron" <dbaron@dbaron.org>
CC: "public-fx@w3.org" <public-fx@w3.org>
Message-ID: <BDF7C000-58EA-476E-A834-879D56F62763@adobe.com>

On Aug 21, 2012, at 2:20 PM, L. David Baron <dbaron@dbaron.org> wrote:

> http://dev.w3.org/csswg/css3-transforms/#three-d-transform-functions

> says that, for rotate3d():
>  # If the direction vector is not of unit length, it will be
>  # normalized.
> Yet http://dev.w3.org/csswg/css3-transforms/#transform-property

> says:
>  # Computed value:     As specified, but with relative lengths
>  #                     converted into absolute lengths. 
> which means that this normalization is not applied to the computed
> value.  Given that it's not applied to the computed value, when *is*
> it applied -- and why does it even matter to say that normalization
> happens?  Or was it intended that the normalization apply to the
> computed value?
I think it should not be applied to the computed value. It might be interesting to have normalization on interpolation. So it seems either be misplaced, or just wrong. This also depends on the decision if we do matrix interpolation or numerical interpolation of rotate3d.

Greetings,
Dirk

> 
> -David
> 
> -- 
> 𝄞   L. David Baron                         http://dbaron.org/   𝄂
> 𝄢   Mozilla                           http://www.mozilla.org/   𝄂
> 

Received on Tuesday, 28 August 2012 05:25:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 28 August 2012 05:25:20 GMT