Use RWH instead of RWHV to know whether a frame is focus.

content/browser/renderer_host/render_widget_host_impl.h

Index: content/browser/renderer_host/render_widget_host_impl.h
diff --git a/content/browser/renderer_host/render_widget_host_impl.h b/content/browser/renderer_host/render_widget_host_impl.h
index 99f2aa3433e4051de1d0b20b9571d2c1a71d742a..12e92b7b2e19de8d2cc20bb45e0a24858636f1c8 100644
--- a/content/browser/renderer_host/render_widget_host_impl.h
+++ b/content/browser/renderer_host/render_widget_host_impl.h
@@ -228,6 +228,9 @@ class CONTENT_EXPORT RenderWidgetHostImpl
   virtual void GotFocus();
   virtual void LostCapture();
 
+  // Indicates whether the frame is currently focused.
+  bool is_focused() const { return is_focused_; }
+
   // Called to notify the RenderWidget that it has lost the mouse lock.
   virtual void LostMouseLock();
 
@@ -841,6 +844,8 @@ class CONTENT_EXPORT RenderWidgetHostImpl
   // object does not self destroy.
   bool owned_by_render_frame_host_;
 
+  bool is_focused_;

[Charlie Reis, 2015/02/02 18:03:55]

It's getting hard to track why we need this here.  Please put a comment saying
why it's need in both RWHI and RWHV, and when (if ever) they differ.

[mlamouri (slow - plz ping), 2015/02/02 18:21:15]

Basically, RWH focus isn't linked to the system while RWHV is. When a frame gets
focused, it will inform the RWH (ViewHostMsg_{Focus,Blur}) so if we want a 1:1
relationship between what the renderer process think and what the browser
process knows, it's better to use that information.

Regarding situations where it differs, it happened in LayoutTests where a frame
was expected to be focused but wasn't according to the browser process.

+
   base::WeakPtrFactory<RenderWidgetHostImpl> weak_factory_;
 
   DISALLOW_COPY_AND_ASSIGN(RenderWidgetHostImpl);