Refactor CSS Transitions to use CSSInterpolationTypes instead of AnimatableValues

third_party/WebKit/LayoutTests/animations/transition-zoomed-length.html

Index: third_party/WebKit/LayoutTests/animations/transition-zoomed-length.html
diff --git a/third_party/WebKit/LayoutTests/animations/transition-zoomed-length.html b/third_party/WebKit/LayoutTests/animations/transition-zoomed-length.html
index 6a8e9f4f332fab740435043189d4bf2d498f759f..516d4d99b96a167481583d0ae20733ac74e9ce17 100644
--- a/third_party/WebKit/LayoutTests/animations/transition-zoomed-length.html
+++ b/third_party/WebKit/LayoutTests/animations/transition-zoomed-length.html
@@ -3,7 +3,6 @@
 <script src="../resources/testharnessreport.js"></script>
 <style>
 #target {
-  transition: 1s;

[alancutter (OOO until 2018), 2017/02/16 04:58:18]

This test was broken. We can't have transitions enabled while we set up the
element's style or we'll trigger erroneous transitions.

I'm not sure why it was passing before but after the transitions refactor it was
properly broken. This patch includes a fix for it.

   border-style: solid;
   outline-style: solid;
   column-rule-style: solid;
@@ -72,6 +71,7 @@ setup(() => {
     target.style[property] = '10px';
     expected[property] = getComputedStyle(target)[property];
   }
+  target.style.transition = '1s';
   internals.setZoomFactor(2);
 });