Put some plug-ins behind an infobar, where they have:...

webkit/plugins/npapi/plugin_group.cc

Index: webkit/plugins/npapi/plugin_group.cc
===================================================================
--- webkit/plugins/npapi/plugin_group.cc	(revision 72249)
+++ webkit/plugins/npapi/plugin_group.cc	(working copy)
@@ -18,6 +18,10 @@
 
 const char* PluginGroup::kAdobeReaderGroupName = "Adobe Reader";
 const char* PluginGroup::kAdobeReaderUpdateURL = "http://get.adobe.com/reader/";
+const char* PluginGroup::kJavaGroupName = "Java";
+const char* PluginGroup::kIcedTeaGroupName = "IcedTea";
+const char* PluginGroup::kQuickTimeGroupName = "QuickTime";
+const char* PluginGroup::kShockwaveGroupName = "Shockwave";
 
 /*static*/
 std::set<string16>* PluginGroup::policy_disabled_plugin_patterns_;
@@ -373,6 +377,13 @@
   return false;
 }
 
+bool PluginGroup::RequiresAuthorization() const {
+  return group_name_ == ASCIIToUTF16(kJavaGroupName) ||

[Bernhard Bauer, 2011/01/24 12:56:33]

I think I'd prefer to reuse the rest of the PluginGroup infrastructure here,
i.e. add an additional bit "Requires authorization" to the PluginGroup
information. That way, we have all the metadata in one place and can reuse the
smart (sorta) plugin matching.

+         group_name_ == ASCIIToUTF16(kIcedTeaGroupName) ||
+         group_name_ == ASCIIToUTF16(kQuickTimeGroupName) ||
+         group_name_ == ASCIIToUTF16(kShockwaveGroupName);
+}
+
 void PluginGroup::DisableOutdatedPlugins() {
   description_ = string16();
   enabled_ = false;