[Android] Upstream the WebView find-in-page API implementation.

content/browser/renderer_host/render_process_host_impl.h

Index: content/browser/renderer_host/render_process_host_impl.h
diff --git a/content/browser/renderer_host/render_process_host_impl.h b/content/browser/renderer_host/render_process_host_impl.h
index 919115addebd1235ce807abf1cfa5207785140f2..f6b171c10e8afbcef55107909b3b373b0708bf8d 100644
--- a/content/browser/renderer_host/render_process_host_impl.h
+++ b/content/browser/renderer_host/render_process_host_impl.h
@@ -11,6 +11,7 @@
 
 #include "base/memory/scoped_ptr.h"
 #include "base/process.h"
+#include "base/synchronization/waitable_event.h"
 #include "base/timer.h"
 #include "content/browser/child_process_launcher.h"
 #include "content/common/content_export.h"
@@ -293,6 +294,14 @@ class CONTENT_EXPORT RenderProcessHostImpl
   // Records the last time we regarded the child process active.
   base::TimeTicks child_process_activity_time_;
 
+#if defined(OS_ANDROID)
+  // Android WebView needs to use a SyncChannel to block the browser process
+  // for synchronous find-in-page API support. In that case the shutdown event
+  // makes no sense but SyncChannel still expects one. So, create a dummy event

[jam, 2012/09/19 16:55:43]

why doesn't it make sense? seems that you'd want to set this when the user
attempts to quit (or the system asks you to?) so that the sync call can be
cancelled? or is this moot because there's no quitting on android?

[Leandro Graciá Gil, 2012/09/19 18:08:59]

AFAIK there's no quitting on Android, we just get killed. Same goes for the
WebView case. I'll be updating the comment to make this clear.

+  // that never will be signaled.
+  base::WaitableEvent dummy_shutdown_event_;
+#endif
+
   // Indicates whether this is a RenderProcessHost of a Browser Plugin guest
   // renderer.
   bool is_guest_;