Plugin Power Saver: Add comprehensive browser tests.

content/renderer/pepper/message_channel.h

Index: content/renderer/pepper/message_channel.h
diff --git a/content/renderer/pepper/message_channel.h b/content/renderer/pepper/message_channel.h
index c3776e922169787c92fada71ef436221917f5d24..57e0d8e4312eeee6e3635c2d39deb8e0adaa994a 100644
--- a/content/renderer/pepper/message_channel.h
+++ b/content/renderer/pepper/message_channel.h
@@ -117,6 +117,9 @@ class MessageChannel :
   // channel's instance synchronously, and return a result.
   void PostBlockingMessageToNative(gin::Arguments* args);
 
+  // Checks if the plugin is marked peripheral. (Only works for test plugins.)
+  void IsPeripheralToNative(gin::Arguments* args);

[tommycli, 2015/04/14 18:30:56]

This is an extremely convenient place to add a JS call, but isn't in the named
purpose of the class.

Should we change this class name to PluginInstanceJavascriptInterface?

Or should we make a new gin::NamedPropertyInterceptor? Can a Pepper plugin have
two gin::NamedPropertyInterceptor members ?

Thanks!

+
   // Post a message to the onmessage handler for this channel's instance
   // synchronously.  This is used by PostMessageToJavaScript.
   void PostMessageToJavaScriptImpl(