Transition to explicit constructors in LayoutUnit

third_party/WebKit/Source/core/editing/VisibleUnits.cpp

Index: third_party/WebKit/Source/core/editing/VisibleUnits.cpp
diff --git a/third_party/WebKit/Source/core/editing/VisibleUnits.cpp b/third_party/WebKit/Source/core/editing/VisibleUnits.cpp
index 358c9b1ae37eaa29b6eab16bc94b8caa69b7b1c1..a8d1a620e30135ef6fc222ff10da1654425e4416 100644
--- a/third_party/WebKit/Source/core/editing/VisibleUnits.cpp
+++ b/third_party/WebKit/Source/core/editing/VisibleUnits.cpp
@@ -1274,9 +1274,9 @@ static inline LayoutPoint absoluteLineDirectionPointToLocalPointInBlock(RootInli
         absoluteBlockPoint -= FloatSize(containingBlock.scrolledContentOffset());
 
     if (root->block().isHorizontalWritingMode())
-        return LayoutPoint(lineDirectionPoint - absoluteBlockPoint.x(), root->blockDirectionPointInLine());
+        return LayoutPoint(LayoutUnit(lineDirectionPoint - absoluteBlockPoint.x()), root->blockDirectionPointInLine());

[eae, 2016/01/29 03:38:11]

lineDirectionPoint - LayoutUnit(absoluteBlockPoint.x())

[leviw_travelin_and_unemployed, 2016/01/29 03:47:27]

This is actually different behavior, and likely changes LayoutTests.

Currently, for float/double operators we convert LayoutUnit to float/double and
do the math on the FPU. I can try it on the bots if you like.

 
-    return LayoutPoint(root->blockDirectionPointInLine(), lineDirectionPoint - absoluteBlockPoint.y());
+    return LayoutPoint(root->blockDirectionPointInLine(), LayoutUnit(lineDirectionPoint - absoluteBlockPoint.y()));

[eae, 2016/01/29 03:38:11]

...and here:

return LayoutPoint(root->blockDirectionPointInLine(), lineDirectionPoint -
LayoutUnit(absoluteBlockPoint.y()));

[leviw_travelin_and_unemployed, 2016/01/29 03:47:27]

Ditto.

 }
 
 VisiblePosition previousLinePosition(const VisiblePosition& visiblePosition, LayoutUnit lineDirectionPoint, EditableType editableType)