Chromium Code Reviews| Index: third_party/WebKit/Source/core/layout/line/InlineBox.cpp |
| diff --git a/third_party/WebKit/Source/core/layout/line/InlineBox.cpp b/third_party/WebKit/Source/core/layout/line/InlineBox.cpp |
| index d07c203204359f08a871b8f826515b7569cea595..3e3e6426c6330aa0963504e4db147a76f81b283b 100644 |
| --- a/third_party/WebKit/Source/core/layout/line/InlineBox.cpp |
| +++ b/third_party/WebKit/Source/core/layout/line/InlineBox.cpp |
| @@ -226,6 +226,8 @@ bool InlineBox::nodeAtPoint(HitTestResult& result, const HitTestLocation& locati |
| if (parent()->lineLayoutItem().hasFlippedBlocksWritingMode()) // Faster than calling containingBlock(). |
| childPoint = layoutObject().containingBlock()->flipForWritingModeForChild(&toLayoutBox(layoutObject()), childPoint); |
| + bool inside = lineLayoutItem().hitTest(result, locationInContainer, childPoint); |
|
pdr.
2016/01/31 21:32:36
The other nodeAtPoint functions follow a pattern w
Miyoung Shin(c)
2016/02/05 23:40:03
Your right. I found out we have only this issue wi
|
| + |
| if (lineLayoutItem().style()->hasBorderRadius()) { |
| LayoutRect borderRect = logicalFrameRect(); |
| borderRect.moveBy(accumulatedOffset); |
| @@ -233,8 +235,7 @@ bool InlineBox::nodeAtPoint(HitTestResult& result, const HitTestLocation& locati |
| if (!locationInContainer.intersects(border)) |
| return false; |
| } |
| - |
| - return lineLayoutItem().hitTest(result, locationInContainer, childPoint); |
| + return inside; |
| } |
| const RootInlineBox& InlineBox::root() const |