CSS filters: fix filtered parent with animated transform child.

third_party/WebKit/Source/core/animation/CompositorAnimations.cpp

Index: third_party/WebKit/Source/core/animation/CompositorAnimations.cpp
diff --git a/third_party/WebKit/Source/core/animation/CompositorAnimations.cpp b/third_party/WebKit/Source/core/animation/CompositorAnimations.cpp
index 776a6d452776a33388b92315943d5b101573c061..ad5124895d3d99666cc8ada06e0f2a305f70c34b 100644
--- a/third_party/WebKit/Source/core/animation/CompositorAnimations.cpp
+++ b/third_party/WebKit/Source/core/animation/CompositorAnimations.cpp
@@ -244,6 +244,11 @@ bool CompositorAnimations::isCandidateForAnimationOnCompositor(const Timing& tim
             if (targetElement.layoutObject() && targetElement.layoutObject()->isInline() && !targetElement.layoutObject()->isInlineBlockOrInlineTable()) {
                 return false;
             }
+            for (LayoutObject* layoutObject = targetElement.layoutObject(); layoutObject; layoutObject = layoutObject->parent()) {
+                if (layoutObject->styleRef().filter().hasReferenceFilter()) {

[chrishtr, 2016/08/11 01:23:59]

All reference filters need css-specified geometry?

[Stephen White, 2016/08/11 15:17:12]

Yes. All reference filters include the "filter region" (the x/y/width/height
attributes on the <filter> node, see
https://drafts.fxtf.org/filters/#filter-region), which is expressed in terms of
the "fractions or percentages of the bounding box on the referencing element".
For hysterical reasons, it defaults to 10% larger than the bounding box (x=-10%,
y=-10%, width=120%, height=120%). So
even the default requires that we know the size.

+                    return false;
+                }
+            }
             transformPropertyCount++;
         }