Index: chrome/browser/autocomplete/keyword_provider.cc |
diff --git a/chrome/browser/autocomplete/keyword_provider.cc b/chrome/browser/autocomplete/keyword_provider.cc |
index 10ae975c95dd33633a927adeee460f7faa4e74a4..2a6c8a6c0aaa40aed5e09dd9c3c77931faf3730b 100644 |
--- a/chrome/browser/autocomplete/keyword_provider.cc |
+++ b/chrome/browser/autocomplete/keyword_provider.cc |
@@ -446,12 +446,6 @@ AutocompleteMatch KeywordProvider::CreateAutocompleteMatch( |
if (!remaining_input.empty() || !keyword_complete || supports_replacement) |
match.fill_into_edit.push_back(L' '); |
match.fill_into_edit.append(remaining_input); |
- // If we wanted to set |result.inline_autocomplete_offset| correctly, we'd |
- // need CleanUserInputKeyword() to return the amount of adjustment it's made |
- // to the user's input. Because right now inexact keyword matches can't score |
- // more highly than a "what you typed" match from one of the other providers, |
- // we just don't bother to do this, and leave inline autocompletion off. |
Peter Kasting
2013/07/16 18:09:05
We should perhaps preserve the comment here about
Mark P
2013/07/16 18:53:23
Okay.
|
- match.inline_autocomplete_offset = string16::npos; |
// Create destination URL and popup entry content by substituting user input |
// into keyword templates. |