W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2017

[csswg-drafts] rotate3d definition could be more explicit about normalization to unit vector

From: Simon Fraser via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Jan 2017 17:40:41 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-200686898-1484329240-sysbot+gh@w3.org>
smfr has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== rotate3d definition could be more explicit about normalization to 
unit vector ==
Migrated from https://www.w3.org/Bugs/Public/show_bug.cgi?id=29417:

https://drafts.csswg.org/css-transforms/#funcdef-rotate3d, rotate3d is
 defined as:

specifies a 3D rotation by the angle specified in last parameter about
 the [x,y,z] direction vector described by the first three parameters.
 A direction vector that cannot be normalized, such as [0,0,0], will 
cause the rotation to not be applied. 

The second sentence implies normalization, but the first could be more
 explicit I think.


(Down in 
https://www.w3.org/TR/css-transforms-1/#interpolation-of-transform-functions,
 it does talk about normalization for rotate3d:

"The transform functions matrix(), matrix3d() and perspective() get 
converted into 4x4 matrices first and interpolated as defined in 
section Interpolation of Matrices afterwards. 

For interpolations with the primitive rotate3d(), the direction 
vectors of the transform functions get normalized first. If the 
normalized vectors are equal, the rotation angle gets interpolated 
numerically.")

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/910 using your GitHub 
account
Received on Friday, 13 January 2017 17:40:47 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:07 UTC