Show alert failure for reloading unpacked extensions with bad manifest

chrome/browser/background/background_contents_service.cc

Index: chrome/browser/background/background_contents_service.cc
diff --git a/chrome/browser/background/background_contents_service.cc b/chrome/browser/background/background_contents_service.cc
index 687d87a3103434423a56b6021e37d3c9bd2bd2c5..6577441fbfd1e57ec37ca9d3238ab581a41250ed 100644
--- a/chrome/browser/background/background_contents_service.cc
+++ b/chrome/browser/background/background_contents_service.cc
@@ -129,7 +129,7 @@ class CrashNotificationDelegate : public NotificationDelegate {
           RestartApplication(copied_extension_id);
     } else {
       extensions::ExtensionSystem::Get(profile_)->extension_service()->
-          ReloadExtension(copied_extension_id);
+          ReloadExtension(copied_extension_id, true);

[Devlin, 2014/07/02 17:46:50]

all of these should have anonymous bool comments...

On second thought.... I'm beginning to doubt whether or not we should force
every caller to do this.  It creates a bit more noise in the CL than I was
expecting.  Let's go back to making two functions,
ReloadExtension() and ReloadExtensionWithQuietFailure().
Sorry for the extra work - I should have looked at all the call sites before I
requested it :/

[gpdavis, 2014/07/02 19:13:54]

Not a problem!  This is why I suggested overloading the method.

The only problem here is that ReloadExtension needs to have the boolean
argument, since it creates and uses the unpacked installer.  The other option
would be having a flag in the class that's used in that method, and another
method to set that flag.  That seems messy, but I couldn't simply add a
ReloadExtensionWithQuietFailure without either copying the method with a minor
change, or adding the boolean flag.  That's why I suggested having one that
takes the boolean flag, and overloading it with one that doesn't that can call
the other with true by default.

I'll take a look at it and see if I can come up with any other solutions.

[Devlin, 2014/07/02 19:16:57]

Our usual tactic for this is something like:
ExtensionService {
 public:
  ReloadExtension() {
    ReloadExtensionImpl(true /* be noisy */);
  }
  ReloadExtensionWithQuietFailure() {
    ReloadExtensionImpl(false /* don't be noisy */);
  }
 private:
  ReloadExtensionImpl(bool be_noisy) {
    ...
  }
}

It keeps the public interface fairly clean, and makes it clear what's happening
in all cases.

     }
 
     // Closing the crash notification balloon for the app/extension here should
@@ -237,7 +237,7 @@ void ReloadExtension(const std::string& extension_id, Profile* profile) {
     // been restarted successfully by someone else (the user).
     return;
   }
-  extension_system->extension_service()->ReloadExtension(extension_id);
+  extension_system->extension_service()->ReloadExtension(extension_id, true);
 }
 
 }  // namespace