commit 15f1e443f22288ee82cde972517ebf3cc1153d97
author Leon Scroggins <scroggo@google.com> Thu Jan 07 15:19:19 2010 -0500
committer Leon Scroggins <scroggo@google.com> Thu Jan 07 15:29:26 2010 -0500
tree 96ee36ee92837ce5452a7eabfbde61aaa6910a85
parent 1ccac4c182607275cdb16213493afa414f0d365e

In motionUp, update the CachedHistory's mMouseBounds.

mMouseBounds is later used to determine the point of clicking.

Fixes http://b/issue?id=2313991

WebKit/android/nav/WebView.cpp

diff --git a/WebKit/android/nav/WebView.cpp b/WebKit/android/nav/WebView.cpp
index 89e6023..1267647 100644
--- a/WebKit/android/nav/WebView.cpp
+++ b/WebKit/android/nav/WebView.cpp
@@ -967,7 +967,9 @@
     }
     DBG_NAV_LOGD("CachedNode:%p (%d) x=%d y=%d rx=%d ry=%d", result,
         result->index(), x, y, rx, ry);
-    setNavBounds(WebCore::IntRect(rx, ry, 1, 1));
+    WebCore::IntRect navBounds = WebCore::IntRect(rx, ry, 1, 1);
+    setNavBounds(navBounds);
+    root->rootHistory()->setMouseBounds(navBounds);
     updateCursorBounds(root, frame, result);
     root->setCursor(const_cast<CachedFrame*>(frame),
         const_cast<CachedNode*>(result));