Omnibox: Add Mid-Input Matching to HistoryQuick Provider

chrome/browser/autocomplete/history_quick_provider.cc

Index: chrome/browser/autocomplete/history_quick_provider.cc
diff --git a/chrome/browser/autocomplete/history_quick_provider.cc b/chrome/browser/autocomplete/history_quick_provider.cc
index d516b970d7b520386b557962ea4cb66ed94b629f..b26a153e248e095c0abec0f81541fcef885a1ad5 100644
--- a/chrome/browser/autocomplete/history_quick_provider.cc
+++ b/chrome/browser/autocomplete/history_quick_provider.cc
@@ -163,8 +163,9 @@ HistoryQuickProvider::~HistoryQuickProvider() {}
 
 void HistoryQuickProvider::DoAutocomplete() {
   // Get the matching URLs from the DB.
-  string16 term_string = autocomplete_input_.text();
-  ScoredHistoryMatches matches = GetIndex()->HistoryItemsForTerms(term_string);
+  ScoredHistoryMatches matches = GetIndex()->HistoryItemsForTerms(
+      autocomplete_input_.text(),
+      autocomplete_input_.cursor_position());

[sky, 2013/02/06 04:59:43]

If the cursor position factors into the results does this mean the query needs
to be rerun when the cursor position changes?

[Mark P, 2013/02/06 17:53:34]

Kind of, yes.  But we decided that in order to avoid disruptive visual changes,
we'd only resend the omnibox query when the input text changes.  This means if
the user puts the cursor in the middle and deletes a character or types a new
character, we'd send a new query, but simply pressing left arrow to get the
middle will not go through tons of changing autocomplete suggestions.  This is
already how the omnibox edit model works, so this changelist needs no additional
changes for that.

   if (matches.empty())
     return;