Index: third_party/WebKit/Source/core/layout/LayoutObject.cpp |
diff --git a/third_party/WebKit/Source/core/layout/LayoutObject.cpp b/third_party/WebKit/Source/core/layout/LayoutObject.cpp |
index 08e8b52a9a9d7a83da6c8f29fc0b6e00641f3cca..ccef0e4d686fbe0047f7d4cccab686dc226671cd 100644 |
--- a/third_party/WebKit/Source/core/layout/LayoutObject.cpp |
+++ b/third_party/WebKit/Source/core/layout/LayoutObject.cpp |
@@ -1385,6 +1385,7 @@ PaintInvalidationReason LayoutObject::invalidatePaintIfNeeded(const PaintInvalid |
// Composited scrolling should not be included in the bounds and position tracking, because the graphics layer backing the scroller |
// does not move on scroll. |
+ // TODO(chrishtr): can we just avoid adding in the scroll in the first place in LayoutBox::mapScrollingContentsRectToBoxSpace? |
if (compositedScrollsWithRespectTo(paintInvalidationContainer)) { |
LayoutSize inverseOffset(toLayoutBox(&paintInvalidationContainer)->scrolledContentOffset()); |
newLocation.move(inverseOffset); |