Skip to content
Browse files

style: Update the expected direction vector of rotate property in wpt.

For interpolations with the primitive rotate3d(), the direction vectors of
the transform functions get normalized first. This should also be applied to
rotate property.

Differential Revision:
  • Loading branch information
BorisChiou authored and emilio committed Nov 18, 2019
1 parent 246433a commit 9a43ad996f87f10a8c61fead3cbbf6460ca2f382
Showing with 7 additions and 2 deletions.
  1. +7 −2 components/style/values/animated/
@@ -1249,7 +1249,11 @@ impl Animate for ComputedRotate {
match (self, other) {
(&Rotate::None, &Rotate::None) => Ok(Rotate::None),
(&Rotate::Rotate3D(fx, fy, fz, fa), &Rotate::None) => {
// No need to normalize `none`, so animate angle directly.
// We always normalize direction vector for rotate3d() first, so we should also
// apply the same rule for rotate property. In other words, we promote none into
// a 3d rotate, and normalize both direction vector first, and then do
// interpolation.
let (fx, fy, fz, fa) = transform::get_normalized_vector_and_angle(fx, fy, fz, fa);
@@ -1258,7 +1262,8 @@ impl Animate for ComputedRotate {
(&Rotate::None, &Rotate::Rotate3D(tx, ty, tz, ta)) => {
// No need to normalize `none`, so animate angle directly.
// Normalize direction vector first.
let (tx, ty, tz, ta) = transform::get_normalized_vector_and_angle(tx, ty, tz, ta);

0 comments on commit 9a43ad9

Please sign in to comment.
You can’t perform that action at this time.