Implement a useful context menu for the blocked plug-in frame:...

chrome/renderer/render_view.h

 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_RENDERER_RENDER_VIEW_H_
 #define CHROME_RENDERER_RENDER_VIEW_H_
 #pragma once
 
 #include <deque>
 #include <map>
@@ skipping 37 matching lines @@
 
 #if defined(OS_WIN)
 // RenderView is a diamond-shaped hierarchy, with WebWidgetClient at the root.
 // VS warns when we inherit the WebWidgetClient method implementations from
 // RenderWidget.  It's safe to ignore that warning.
 #pragma warning(disable: 4250)
 #endif
 
 class AudioMessageFilter;
 class AutoFillHelper;
+class CustomMenuListener;
 class DictionaryValue;
 class DeviceOrientationDispatcher;
 class DevToolsAgent;
 class DevToolsClient;
 class DomAutomationController;
 class DOMUIBindings;
 class ExternalHostBindings;
 class FilePath;
 class GeolocationDispatcherOld;
 class GURL;
@@ skipping 262 matching lines @@
   // Create a new plugin without checking the content settings.
   WebKit::WebPlugin* CreatePluginNoCheck(WebKit::WebFrame* frame,
                                          const WebKit::WebPluginParams& params);
 
   // Asks the browser for the CPBrowsingContext associated with this renderer.
   // This is an opaque identifier associated with the renderer for sending
   // messages for the given "Chrome Plugin." The Chrome Plugin API is used
   // only by gears and this function can be deleted when we remove gears.
   uint32 GetCPBrowsingContext();
 
+  // Handles registering and deregistering customer handlers for custom
+  // context menu events.

[brettw, 2010/12/08 07:20:13]

Can you add a quick extra sentence here about how to show a context menu. I'm
thinking like "To show a manu call chowContextMenu and then immediately
afterward call CustomMenuListenerInstall to install yourself as the receiver for
the the asynchronous reply."

[Chris Evans, 2010/12/08 16:33:52]

Done.

+  void CustomMenuListenerInstall(CustomMenuListener* listening);
+  void CustomMenuListenerDestroyed(CustomMenuListener* dead);
+
 #if defined(OS_MACOSX)
   // Enables/disabled plugin IME for the given plugin.
   void SetPluginImeEnabled(bool enabled, int plugin_id);
 
   // Helper routines for accelerated plugin support. Used by the
   // WebPluginDelegateProxy, which has a pointer to the RenderView.
   gfx::PluginWindowHandle AllocateFakePluginWindowHandle(bool opaque,
                                                          bool root);
   void DestroyFakePluginWindowHandle(gfx::PluginWindowHandle window);
   void AcceleratedSurfaceSetIOSurface(gfx::PluginWindowHandle window,
@@ skipping 1108 matching lines @@
   // Allows DOM UI pages (new tab page, etc.) to talk to the browser. The JS
   // object is only exposed when DOM UI bindings are enabled.
   scoped_ptr<DOMUIBindings> dom_ui_bindings_;
 
   // External host exposed through automation controller.
   scoped_ptr<ExternalHostBindings> external_host_bindings_;
 
   // The external popup for the currently showing select popup.
   scoped_ptr<ExternalPopupMenu> external_popup_menu_;
 
+  // The custom menu event listener, if any.
+  CustomMenuListener* custom_menu_listener_;
+
   // ---------------------------------------------------------------------------
   // ADDING NEW DATA? Please see if it fits appropriately in one of the above
   // sections rather than throwing it randomly at the end. If you're adding a
   // bunch of stuff, you should probably create a helper class and put your
   // data and methods on that to avoid bloating RenderView more.
   // ---------------------------------------------------------------------------
 
   DISALLOW_COPY_AND_ASSIGN(RenderView);
 };
 
 #endif  // CHROME_RENDERER_RENDER_VIEW_H_