Use slop to determine the node used for anchoring top/left.

Certain sites use tables for layout and padding elements instead of
standard CSS. If the exact scrollX/Y is used to find the anchor,
hit test result may return an incorrect node. A little bit of slop
helps in finding the correct node, if necessary.

Bug: 5291151
Change-Id: I13e8d2b04ef5049c14c299be42c6699c3d0c945e

1 files changed, 10 insertions, 0 deletions

diff --git a/Source/WebKit/android/jni/WebViewCore.cpp b/Source/WebKit/android/jni/WebViewCore.cpp
index e621644..1fe4a1d 100644
--- a/Source/WebKit/android/jni/WebViewCore.cpp
+++ b/Source/WebKit/android/jni/WebViewCore.cpp
@@ -1164,6 +1164,16 @@ void WebViewCore::setSizeScreenWidthAndScale(int width, int height,
                         m_mainFrame->eventHandler()->hitTestResultAtPoint(
                                 anchorPoint, false);
                 node = hitTestResult.innerNode();
+                if (node && !node->isTextNode()) {
+                    // If the hitTestResultAtPoint didn't find a suitable node
+                    // for anchoring, try again with some slop.
+                    static const int HIT_SLOP = 30;
+                    anchorPoint.move(HIT_SLOP, HIT_SLOP);
+                    hitTestResult =
+                        m_mainFrame->eventHandler()->hitTestResultAtPoint(
+                                anchorPoint, false);
+                    node = hitTestResult.innerNode();
+                }
             }
             if (node) {
                 bounds = node->getRect();