Make Google Search autocomplete provider cursor aware.

chrome/browser/autocomplete/history_provider.cc

Index: chrome/browser/autocomplete/history_provider.cc
diff --git a/chrome/browser/autocomplete/history_provider.cc b/chrome/browser/autocomplete/history_provider.cc
index e9495d120b851e6154515b9b695933d3455c9f91..669dc128209fa26ddd1c7ab568ca7f6b327ff38f 100644
--- a/chrome/browser/autocomplete/history_provider.cc
+++ b/chrome/browser/autocomplete/history_provider.cc
@@ -134,7 +134,10 @@ bool HistoryProvider::FixupUserInput(AutocompleteInput* input) {
 
   url_parse::Parsed parts;
   URLFixerUpper::SegmentURL(output, &parts);
-  input->UpdateText(output, parts);
+  // TODO: Rather then risking bogus cursor location, we simply pretend it was
+  // not set.  It should be fine as long as the current implementation is not
+  // cursor aware (which is true as of Nov 2012).

[Peter Kasting, 2012/12/05 20:49:38]

We probably should do the right thing here, since Mark wants to make the history
system cursor-aware (separate bug on file).  We can mostly handle things with
manual adjustments or using the conversion functions in
utf_offset_conversions.h.  The big piece is that we probably have to make
FixupURL() handle offset adjustment, which is nasty.

This could all be done as a separate change to limit scope creep.  In that case
I'd change the TODO text here to refer to what needs to be done.

[Bart N., 2012/12/06 21:43:32]

Done.

+  input->UpdateText(output, string16::npos, parts);
   return !output.empty();
 }