Create a visible window with class name Chrome_RenderWidgetHostHWND which corresponds to the bounds…

content/browser/renderer_host/render_widget_host_view_aura.h

Index: content/browser/renderer_host/render_widget_host_view_aura.h
===================================================================
--- content/browser/renderer_host/render_widget_host_view_aura.h	(revision 248647)
+++ content/browser/renderer_host/render_widget_host_view_aura.h	(working copy)
@@ -67,6 +67,10 @@
 }
 
 namespace content {
+#if defined(OS_WIN)
+class LegacyRenderWidgetHostHWND;
+#endif
+
 class RenderWidgetHostImpl;
 class RenderWidgetHostView;
 class ResizeLock;
@@ -800,10 +804,12 @@
   base::WeakPtrFactory<RenderWidgetHostViewAura> weak_ptr_factory_;
 
 #if defined(OS_WIN)
-  // The dummy HWND which corresponds to the bounds of the web page. This is
-  // passed to windowless plugins like Flash/Silverlight, etc as the
-  // container window.
-  HWND plugin_parent_window_;
+  // The LegacyRenderWidgetHostHWND class provides a dummy HWND which is used
+  // for accessibility, as the container for windowless plugins like
+  // Flash/Silverlight, etc and for legacy drivers for trackpoints/trackpads,
+  // etc.
+  // This instance is deleted when the parent window is destroyed.
+  content::LegacyRenderWidgetHostHWND* legacy_render_widget_host_HWND_;

[sky, 2014/02/05 15:22:44]

What are the advantages of wiring LegacyRenderWidgetHostHWND at RWHVA instead of
WebContentsViewAura?

[ananta, 2014/02/05 16:35:51]

RWHVA has plumbing code to track when its aura::Window is added to the
RootWindow, which is used to reparent the container HWND as needed. This is
needed for plugins to work correctly. 

 #endif
   DISALLOW_COPY_AND_ASSIGN(RenderWidgetHostViewAura);
 };