Look Up on Force Touch

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

Index: third_party/WebKit/Source/core/editing/SelectionController.cpp
diff --git a/third_party/WebKit/Source/core/editing/SelectionController.cpp b/third_party/WebKit/Source/core/editing/SelectionController.cpp
index 4f74bd149e559af1c3bac79731c5106b7ee23395..ef214d9c63bbbea59cc36bbd7263faad3a0a8901 100644
--- a/third_party/WebKit/Source/core/editing/SelectionController.cpp
+++ b/third_party/WebKit/Source/core/editing/SelectionController.cpp
@@ -543,6 +543,22 @@ bool SelectionController::handleMouseReleaseEvent(const MouseEventWithHitTestRes
     return handleMouseReleaseEventAlgorithm<EditingStrategy>(event, dragStartPos);
 }
 
+bool SelectionController::selectWordAtPositionIfAny(const IntPoint& position)
+{
+    HitTestRequest request(HitTestRequest::Active);
+    HitTestResult result(request, position);
+    m_frame->document()->layoutView()->hitTest(result);

[Rick Byers, 2015/12/21 16:31:08]

You just did a hit-test up in WebViewImpl, it's a shame to do another one (hit
tests are expensive).  Can you instead do a single hit-test in WebViewImpl and
take a HitTestResults in your SelectionController API?  That would also make it
a lot closer to existing APIs like selectClosestWordFromMouseEvent and
handleMousePressEventDoubleClick.  I think there's been some effort to eliminate
unnecessary hit tests from inside the editing code.

[spqchan, 2016/01/06 22:52:31]

Done.

+
+    if (result.scrollbar()
+        || result.isLiveLink()
+        || !(selection().isContentEditable()
+        || (result.innerNode() && result.innerNode()->isTextNode())))
+        return false;
+
+    selectClosestWordFromHitTestResult<EditingStrategy>(result, AppendTrailingWhitespace::DontAppend);
+    return true;
+}
+
 bool SelectionController::handlePasteGlobalSelection(const PlatformMouseEvent& mouseEvent)
 {
     // If the event was a middle click, attempt to copy global selection in after