Show a replacement plug-in for loading errors.

webkit/plugins/ppapi/ppapi_webplugin_impl.cc

Index: webkit/plugins/ppapi/ppapi_webplugin_impl.cc
diff --git a/webkit/plugins/ppapi/ppapi_webplugin_impl.cc b/webkit/plugins/ppapi/ppapi_webplugin_impl.cc
index fb0166217f54a830cb8e15b846286d0fc8b7e641..1b6701fb613a686d055b63b357ce12bda287824f 100644
--- a/webkit/plugins/ppapi/ppapi_webplugin_impl.cc
+++ b/webkit/plugins/ppapi/ppapi_webplugin_impl.cc
@@ -84,7 +84,16 @@ bool WebPluginImpl::initialize(WebPluginContainer* container) {
   if (!success) {
     instance_->Delete();
     instance_ = NULL;
-    return false;
+
+    WebKit::WebPlugin* replacement_plugin =
+        init_data_->delegate->CreatePluginReplacement(
+            init_data_->module->path());
+    if (!replacement_plugin->initialize(container)) {
+      LOG(ERROR) << "Couldn't initialize replacement plug-in";

[darin (slow to review), 2012/04/30 18:57:02]

do we really need all of these LOG(ERROR) statements in this patch?  just use
DLOG(ERROR) instead?  or, are you really hoping to collect chrome_debug.log
files from end users?

[Bernhard Bauer, 2012/04/30 19:30:36]

Right; I do want logging if we can't load the actual plug-in, but the
replacement plug-in won't ever fail as long as it is a WebViewPlugin.

+      return false;
+    }
+    container->setPlugin(replacement_plugin);
+    return true;
   }
 
   init_data_.reset();