Invalidate ancestor resources in when relative lengths change

Source/core/layout/svg/LayoutSVGResourceContainer.cpp

Index: Source/core/layout/svg/LayoutSVGResourceContainer.cpp
diff --git a/Source/core/layout/svg/LayoutSVGResourceContainer.cpp b/Source/core/layout/svg/LayoutSVGResourceContainer.cpp
index 35ac287f07d068fe010c527b914d6865a438a8e8..4fd603b387f397067b754df7fe36e6c92e2a6f77 100644
--- a/Source/core/layout/svg/LayoutSVGResourceContainer.cpp
+++ b/Source/core/layout/svg/LayoutSVGResourceContainer.cpp
@@ -274,13 +274,13 @@ static inline void removeFromCacheAndInvalidateDependencies(LayoutObject* object
     }
 }
 
-void LayoutSVGResourceContainer::markForLayoutAndParentResourceInvalidation(LayoutObject* object, bool needsLayout)
+void LayoutSVGResourceContainer::markForLayoutAndParentResourceInvalidation(LayoutObject* object, bool needsLayout, SubtreeLayoutScope* layoutScope)
 {
     ASSERT(object);
     ASSERT(object->node());
 
     if (needsLayout && !object->documentBeingDestroyed())
-        object->setNeedsLayoutAndFullPaintInvalidation(LayoutInvalidationReason::SvgResourceInvalidated);
+        object->setNeedsLayoutAndFullPaintInvalidation(LayoutInvalidationReason::SvgResourceInvalidated, MarkContainerChain, layoutScope);

[fs, 2015/04/30 13:36:47]

I suppose we should work to thread the layout scope even further. Pretty big
change that though. *puts on mental TODO*

 
     removeFromCacheAndInvalidateDependencies(object, needsLayout);