Remove installation of Chrome Frame.

chrome/installer/setup/install.cc

Index: chrome/installer/setup/install.cc
diff --git a/chrome/installer/setup/install.cc b/chrome/installer/setup/install.cc
index c8b071ce2d0cb37735ff6da664190179da6795df..2902d8ec2528712e4e47723b1d9b9ec6bb9176c7 100644
--- a/chrome/installer/setup/install.cc
+++ b/chrome/installer/setup/install.cc
@@ -507,17 +507,7 @@ InstallStatus InstallOrUpdateProduct(
     const base::FilePath& prefs_path,
     const MasterPreferences& prefs,
     const Version& new_version) {
-  // TODO(robertshield): Removing the pending on-reboot moves should be done
-  // elsewhere.
-  // TODO(erikwright): Understand why this is Chrome Frame only and whether
-  // it also applies to App Host. Shouldn't it apply to any multi-install too?
-  const Products& products = installer_state.products();
-  DCHECK(products.size());
-  if (installer_state.FindProduct(BrowserDistribution::CHROME_FRAME)) {
-    // Make sure that we don't end up deleting installed files on next reboot.
-    if (!RemoveFromMovesPendingReboot(installer_state.target_path()))

[gab, 2013/12/19 01:18:31]

This appears to have been the only remaining call to this method; remove it too?

[grt (UTC plus 2), 2013/12/19 20:57:06]

I've re-added Erik's TODO since I think it still applies. I wonder if there's
actually a bug here for the non-Chrome Frame case.

[gab, 2013/12/20 19:05:54]

Hmmm... so we're going to leave a call that's used by nobody else than a
comment?!

I don't actually want this CL to take this on, but we should make an action item
(i.e. a bug + link to bug in comment) to promptly look into this, rotting
unreachable code isn't desired.

[grt (UTC plus 2), 2013/12/23 17:58:34]

Well, when you put it that way...
Agreed. To play devil's advocate, though, it will rot no more or less now than
it would have before since it has test coverage.

I've noodled in my noodle about Erik's concern. From memory, this was needed for
Chrome Frame but not Chrome since the installer requires the user to quit Chrome
before proceeding. As such, uninstalling Chrome should always be able to delete
the files without having to resort to the DeleteAfterRebootHelper. In practice,
there is a race so perhaps the safest thing to do is to leave the call here for
all products. I can't think of a downside to this, so I've made it so.

Thanks for pushing back on this.

-      LOG(ERROR) << "Error accessing pending moves value.";
-  }
+  DCHECK(installer_state.products().size());

[gab, 2013/12/19 01:18:31]

Replace check for foo.size(), but !foo.empty()

[grt (UTC plus 2), 2013/12/19 20:57:06]

Done.

 
   // Create VisualElementManifest.xml in |src_path| (if required) so that it
   // looks as if it had been extracted from the archive when calling