Teach SVGImageForContainer::imageForCurrentFrame about the URL

third_party/WebKit/Source/core/svg/graphics/SVGImageForContainer.cpp

Index: third_party/WebKit/Source/core/svg/graphics/SVGImageForContainer.cpp
diff --git a/third_party/WebKit/Source/core/svg/graphics/SVGImageForContainer.cpp b/third_party/WebKit/Source/core/svg/graphics/SVGImageForContainer.cpp
index 65df96284dea7116ce8d184ecd86112f01097928..57f9e7bd2011d17da8cfaf24a235d590d08ea9f4 100644
--- a/third_party/WebKit/Source/core/svg/graphics/SVGImageForContainer.cpp
+++ b/third_party/WebKit/Source/core/svg/graphics/SVGImageForContainer.cpp
@@ -49,7 +49,7 @@ void SVGImageForContainer::drawPattern(GraphicsContext* context, const FloatRect
 
 PassRefPtr<SkImage> SVGImageForContainer::imageForCurrentFrame()
 {
-    return m_image->imageForCurrentFrame();
+    return m_image->imageForCurrentFrameForContainer(m_url);

[fs, 2015/12/03 15:45:19]

Shouldn't we potentially be passing containerSize here as well, or is that
something for a rainier day?

[davve, 2015/12/03 21:07:57]

Potentially, yes. I haven't really investigated the implications.
imageForCurrentFrame() uses the intrinsic size (with 300x150 fallback) as
container size, which does cause some issues. Especially the 2:1 ratio it gives
for SVG images without any intrinsic dimensions.

I'll investigate more tomorrow, but I wouldn't mind following up in another CL.

[fs, 2015/12/03 21:15:11]

Keeping it for later SGTM.

 }
 
 } // namespace blink