Chromium Code Reviews| 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 85469ef8baeb70befcdbb797f57ebe3e3d300a91..97ca75f7f2f80afcfaba3faa426c4eaadf54569a 100644 |
| --- a/third_party/WebKit/Source/core/layout/LayoutObject.cpp |
| +++ b/third_party/WebKit/Source/core/layout/LayoutObject.cpp |
| @@ -1659,8 +1659,10 @@ void LayoutObject::showLayoutTreeForThis() const |
| void LayoutObject::showLineTreeForThis() const |
| { |
| - if (containingBlock()) |
| - containingBlock()->showLineTreeAndMark(0, 0, 0, 0, this); |
| + if (LayoutBlock* cb = containingBlock()) { |
| + if (cb->isLayoutBlockFlow()) |
|
wkorman
2016/05/04 20:30:41
Does this change behavior of what we output at all
mstensho (USE GERRIT)
2016/05/04 20:54:25
In theory, yes. If someone wants to display the li
|
| + toLayoutBlockFlow(cb)->showLineTreeAndMark(0, 0, 0, 0, this); |
|
wkorman
2016/05/04 20:30:41
Use nullptr rather than 0. Is it untoward re: cons
mstensho (USE GERRIT)
2016/05/04 20:54:25
Done.
|
| + } |
| } |
| void LayoutObject::showLayoutObject() const |