LayoutBox::mapContentsRectToVisibleRectInBorderBoxSpace()

third_party/WebKit/Source/core/layout/LayoutBox.h

Index: third_party/WebKit/Source/core/layout/LayoutBox.h
diff --git a/third_party/WebKit/Source/core/layout/LayoutBox.h b/third_party/WebKit/Source/core/layout/LayoutBox.h
index 9df0837d692dd63be5519b4d0506d08062707466..6adaa7735d1ec04c2cbd1bbf8ea9573605de42dd 100644
--- a/third_party/WebKit/Source/core/layout/LayoutBox.h
+++ b/third_party/WebKit/Source/core/layout/LayoutBox.h
@@ -841,7 +841,9 @@ public:
     virtual bool needsPreferredWidthsRecalculation() const;
 
     IntSize scrolledContentOffset() const;
-    void mapScrollingContentsRectToBoxSpace(LayoutRect&) const;
+
+    // See LayoutObject::mapToVisibleRectInAncestorSpace() for the meaning of return value.
+    bool mapContentsRectToVisibleRectInBorderBoxSpace(LayoutRect&, VisibleRectFlags) const;

[chrishtr, 2016/03/28 20:38:59]

This is not a visual rect right? Because it doesn't flip for writing mode, for
example?

[Xianzhu, 2016/03/28 21:12:08]

Right. I'm going to modify mapToVisibleRectInAncestorSpace() to accept visual
rect (flipped for writing mode), so that this function can also always accept
and output visible rect.

 
     // Returns true if the rect actually intersects the clipping region.
     // If edgeInclusive is true, then this method may return true even