Omnibox: Make the Controller Reorder Matches for Inlining

chrome/browser/autocomplete/autocomplete_match.h

Index: chrome/browser/autocomplete/autocomplete_match.h
diff --git a/chrome/browser/autocomplete/autocomplete_match.h b/chrome/browser/autocomplete/autocomplete_match.h
index 4d4ca47c363849ff42a5b2d4b409c9b2fefff693..68887461ce5e7adfdc34ae3019fc940e7d1d3185 100644
--- a/chrome/browser/autocomplete/autocomplete_match.h
+++ b/chrome/browser/autocomplete/autocomplete_match.h
@@ -251,6 +251,10 @@ struct AutocompleteMatch {
   // not be inline autocompleted.
   size_t inline_autocomplete_offset;
 
+  // If false, the omnibox should prevent this match from being the default
+  // match.

[Peter Kasting, 2013/07/17 18:29:48]

Nit: I might add something like:

Providers should set this to true only if the user's input, plus any inline
autocompletion on this match, would lead the user to expect a navigation to this
match's destination URL.  For example, with input "foo", a search for "bar" or
navigation to "bar.com" should not set this flag; a navigation to "foo.com"
should only set this flag if ".com" will be inline autocompleted; and a
navigation to "foo/" (an intranet host) or search for "foo" could (and probably
should) set this flag.

[Mark P, 2013/07/17 20:39:18]

That's a good explanation.  Inserted with minor editing.

+  bool allowed_to_be_default_match;
+
   // The URL to actually load when the autocomplete item is selected. This URL
   // should be canonical so we can compare URLs with strcmp to avoid dupes.
   // It may be empty if there is no possible navigation.