Omnibox: Don't Force Notify Default Match Changed When Expiring Old Matches

chrome/browser/autocomplete/autocomplete_controller.cc

Index: chrome/browser/autocomplete/autocomplete_controller.cc
diff --git a/chrome/browser/autocomplete/autocomplete_controller.cc b/chrome/browser/autocomplete/autocomplete_controller.cc
index e7453814185ce8d8faa320072d3444253a70b210..26f53903625f58c2084dcd171b5e44a9d4f4a4a2 100644
--- a/chrome/browser/autocomplete/autocomplete_controller.cc
+++ b/chrome/browser/autocomplete/autocomplete_controller.cc
@@ -279,12 +279,7 @@ void AutocompleteController::ExpireCopiedEntries() {
   // The first true makes UpdateResult() clear out the results and
   // regenerate them, thus ensuring that no results from the previous
   // result set remain.
-  // The second true says to pretend the default match changed (even
-  // if it did not).  This may not be necessary but the code has been
-  // like this for a long time and there's probably no great benefit in
-  // changing it.  Classically we have erred on the side of notifying
-  // too often because it hasn't had any major side effects.
-  UpdateResult(true, true);
+  UpdateResult(true, false);
 }
 
 void AutocompleteController::OnProviderUpdate(bool updated_matches) {