Make Omnibox's HistoryQuickProvider's new scoring less aggressive

chrome/browser/history/scored_history_match.cc

Index: chrome/browser/history/scored_history_match.cc
diff --git a/chrome/browser/history/scored_history_match.cc b/chrome/browser/history/scored_history_match.cc
index d71b9740811162c2d8a35be779587e368843cbd9..dee31c81b6ba49cffba66d8845b2f57b75755b40 100644
--- a/chrome/browser/history/scored_history_match.cc
+++ b/chrome/browser/history/scored_history_match.cc
@@ -119,13 +119,11 @@ ScoredHistoryMatch::ScoredHistoryMatch(const URLRow& row,
 
     // Combine recency, popularity, and topicality scores into one.
     // Example of how this functions: Suppose the omnibox has one
-    // input term.  Suppose we have a URL that has 8 typed visits with
+    // input term.  Suppose we have a URL that has 30 typed visits with
     // the most recent being within a day and the omnibox input term
     // has a single URL hostname hit at a word boundary.  Then this
-    // URL will score 1300 ( = 8 * 162.5), which is exactly the value of
-    // search what you type.  That is, it's the boundary of what might
-    // end up being inlined.
-    raw_score = 162.5 * topicality_score * recency_score * popularity_score;
+    // URL will score 1200 ( = 30 * 40.0).
+    raw_score = 40.0 * topicality_score * recency_score * popularity_score;
     raw_score =
         (raw_score <= kint32max) ? static_cast<int>(raw_score) : kint32max;
   } else {  // "old" scoring