Render Core Animation plugins through WebKit's compositor rather than

content/common/plugin_messages.h

Index: content/common/plugin_messages.h
===================================================================
--- content/common/plugin_messages.h	(revision 111400)
+++ content/common/plugin_messages.h	(working copy)
@@ -382,6 +382,9 @@
 
 IPC_MESSAGE_ROUTED0(PluginHostMsg_StartIme)
 
+//----------------------------------------------------------------------
+// Legacy Core Animation plugin implementation rendering directly to screen.
+
 // This message, used in Mac OS X 10.5 and earlier, is sent from the plug-in
 // process to the renderer process to indicate that the plug-in allocated a
 // new TransportDIB that holds the GPU's rendered image.  This information is
@@ -435,6 +438,31 @@
 IPC_MESSAGE_ROUTED2(PluginHostMsg_AcceleratedSurfaceBuffersSwapped,
                     gfx::PluginWindowHandle /* window */,
                     uint64 /* surface_id */)
+
+//----------------------------------------------------------------------
+// New Core Animation plugin implementation rendering via compositor.
+
+// Notifies the renderer process that this plugin will be using the
+// accelerated rendering path. |opaque| indicates whether the content
+// should be treated as opaque.
+IPC_MESSAGE_ROUTED1(PluginHostMsg_AcceleratedPluginEnabledRendering,
+                    bool /* opaque */)

[stuartmorgan, 2011/11/28 10:09:04]

Do we expect to need opaque in the future for some non-NPAPI use? CA plugins
should always be considered transparent, so if not we can remove this argument.
IIRC the argument on the other function was when we were trying to hack up an
intermediate state where some CA plugins were opaque and others weren't, as a
stopgap to having compositing.

[Ken Russell (switch to Gerrit), 2011/11/28 23:40:15]

I wasn't sure whether the opaque flag was needed. I vaguely recall that it was
needed to distinguish between Core Animation and Pepper 3D. Removed.

+
+// Notifies the renderer process that the plugin allocated a new
+// IOSurface into which it is rendering. The renderer process forwards
+// this IOSurface to the GPU process, causing it to be bound to a
+// texture from which the compositor can render. Any previous
+// IOSurface allocated by this plugin must be implicitly released by
+// the receipt of this message.
+IPC_MESSAGE_ROUTED3(PluginHostMsg_AcceleratedPluginAllocatedIOSurface,
+                    int32 /* width */,
+                    int32 /* height */,
+                    uint32 /* surface_id */)
+
+// Notifies the renderer process that the plugin produced a new frame
+// of content into its IOSurface, and therefore that the compositor
+// needs to redraw.
+IPC_MESSAGE_ROUTED0(PluginHostMsg_AcceleratedPluginSwappedIOSurface)
 #endif
 
 IPC_MESSAGE_CONTROL1(PluginHostMsg_ClearSiteDataResult,