Refactoring out the code in LayoutTreeAsText::writeLayoutObject.

third_party/WebKit/Source/core/layout/LayoutInline.cpp

Index: third_party/WebKit/Source/core/layout/LayoutInline.cpp
diff --git a/third_party/WebKit/Source/core/layout/LayoutInline.cpp b/third_party/WebKit/Source/core/layout/LayoutInline.cpp
index 5277c70df08b6b99419fb3e7eac9adb45e4206d4..1f7662e410be6c84d082880b426021eb91f39416 100644
--- a/third_party/WebKit/Source/core/layout/LayoutInline.cpp
+++ b/third_party/WebKit/Source/core/layout/LayoutInline.cpp
@@ -1369,4 +1369,14 @@ void LayoutInline::invalidateDisplayItemClients(PaintInvalidationReason invalida
         paintInvalidator.invalidateDisplayItemClient(*box, invalidationReason);
 }
 
+// FIXME: Would be better not to just dump 0, 0 as the x and y here.

[benjhayden, 2016/08/29 20:45:27]

Would it be possible to go ahead and use linesBox.x() and linesBox.y() in this
CL so as not to break TracedLayoutObject? I realize that might mean updating a
bunch of layout tests, but perhaps layout-dev has a feasible way to do that?

[lunalu1, 2016/08/30 20:35:30]

I will use linesBox.x() and linesBox.y() for now, and figure out which layout
tests to be updated later. 

+LayoutRect LayoutInline::debugRect() const
+{
+    IntRect linesBox = enclosingIntRect(linesBoundingBox());
+    LayoutRect r = LayoutRect(IntRect(IntRect(0, 0, linesBox.width(), linesBox.height())));
+
+    setLayoutRectDimForLayoutView(r);
+    return r;
+}
+
 } // namespace blink