Notify Windows Shell after making Chrome default interactively

chrome/installer/util/shell_util.cc

Index: chrome/installer/util/shell_util.cc
diff --git a/chrome/installer/util/shell_util.cc b/chrome/installer/util/shell_util.cc
index 582ef07bde29f55ce79f8cd2ba5b907f64f1d17c..576f3442a8f7f8169efb5e5405d0ecc27d89a1b1 100644
--- a/chrome/installer/util/shell_util.cc
+++ b/chrome/installer/util/shell_util.cc
@@ -1182,7 +1182,10 @@ bool ShellUtil::ShowMakeChromeDefaultSystemUI(BrowserDistribution* dist,
   // "Set Program Associations" section of the "Default Programs"
   // control panel, which is a mess, or pop the concise "How you want to open
   // webpages?" dialog.  We choose the latter.
-  return LaunchSelectDefaultProtocolHandlerDialog(L"http");
+  bool success = LaunchSelectDefaultProtocolHandlerDialog(L"http");
+  if (success)
+    SHChangeNotify(SHCNE_ASSOCCHANGED, SHCNF_IDLIST, NULL, NULL);

[grt (UTC plus 2), 2012/06/19 03:36:24]

how about moving this into LaunchSelectDefaultProtocolHandlerDialog?  it should
be safe to do the notify after prompting for other protocols.  if the shell's
handling of http is buggy, maybe it is for others as well.  by the same token,
if we're actually supposed to do the notify after the Open With dialog goes
away, then we definitely want to do this for all protocols.

[gab, 2012/06/19 04:12:13]

Good call, Done.

+  return success;
 }
 
 bool ShellUtil::MakeChromeDefaultProtocolClient(BrowserDistribution* dist,