Upstream the Android port find-in-page feature.

chrome/browser/ui/find_bar/find_tab_helper.h

Index: chrome/browser/ui/find_bar/find_tab_helper.h
diff --git a/chrome/browser/ui/find_bar/find_tab_helper.h b/chrome/browser/ui/find_bar/find_tab_helper.h
index be11ed9e87784899d82d42ed99e67e82d24453a0..846017d87e7b2d9bfb1f73411d28e968b93a7c8d 100644
--- a/chrome/browser/ui/find_bar/find_tab_helper.h
+++ b/chrome/browser/ui/find_bar/find_tab_helper.h
@@ -9,6 +9,10 @@
 #include "chrome/browser/ui/find_bar/find_notification_details.h"
 #include "content/public/browser/web_contents_observer.h"
 
+namespace gfx {
+class RectF;
+}
+
 // Per-tab find manager. Handles dealing with the life cycle of find sessions.
 class FindTabHelper : public content::WebContentsObserver {
  public:
@@ -57,6 +61,19 @@ class FindTabHelper : public content::WebContentsObserver {
     return last_search_result_;
   }
 
+#if defined(OS_ANDROID)
+  // Selects and zooms to the find result nearest to the point (x,y)
+  // defined in find-in-page coordinates.
+  void ActivateNearestFindResult(float x, float y);
+
+  // Asks the renderer to send the rects of the current find matches.
+  void RequestFindMatchRects(int current_version);
+
+  void HandleGetFindMatchRectsReply(int version,

[jam, 2012/09/04 16:39:09]

it seems very unnecessary that chrome_web_contents_delegate_android.cc calls
this android-only method, which right before it registered for the notification
which it fires, and then it listens to the notifications it fires and calls code
as a result. i.e. this method should be removed, and
chrome_web_contents_delegate_android.cc should just do what it does in response
to the notification inline

[Leandro Graciá Gil, 2012/09/04 18:25:50]

This was done this way in order to get a symmetrical design and behaviour with
the find results and have FindTabHelper handle both the requests and replies for
all find-in-page operations. Also, it seems that the idea of tapping to find
results to go to them caught some attention while upstreaming the WebKit side.
Because of that I tried to make this simple to be adopted by Desktop in the
future in case we decide so. Furthermore, we might require this in the future if
at some point this reply needs to check the FindTabHelper status.

However, as you point we need no state check for this reply so it should be
possible to call directly from ChromeWebContentsDelegateAndroid for now.

I'll be removing this from here in the next iteration of the patch. If you
change your mind just tell me and I'll bring it in again.

+                                    const std::vector<gfx::RectF>& rects,
+                                    const gfx::RectF& active_rect);
+#endif
+
   void HandleFindReply(int request_id,
                        int number_of_matches,
                        const gfx::Rect& selection_rect,