Always allow exact match non-substituting keywords.

chrome/browser/autocomplete/keyword_provider.h

Index: chrome/browser/autocomplete/keyword_provider.h
diff --git a/chrome/browser/autocomplete/keyword_provider.h b/chrome/browser/autocomplete/keyword_provider.h
index bd5cb9e851f06598f0247cd69d10590bca548202..348eb7e32b9d12261b8c4ffa70ba897893c085a4 100644
--- a/chrome/browser/autocomplete/keyword_provider.h
+++ b/chrome/browser/autocomplete/keyword_provider.h
@@ -109,14 +109,14 @@ class KeywordProvider : public AutocompleteProvider,
       AutocompleteMatch* match);
 
   // Determines the relevance for some input, given its type, whether the user
-  // typed the complete keyword, and whether the keyword needs query text (true
-  // if the keyword supports replacement and the user isn't in "prefer keyword
-  // matches" mode).
+  // typed the complete keyword, and whether the user is in "prefer keyword
+  // matches" mode, and whether the keyword supports replacement.
   // If |allow_exact_keyword_match| is false, the relevance for complete
-  // keywords is degraded.
+  // keywords that support replacements is degraded.
   static int CalculateRelevance(AutocompleteInput::Type type,
                                 bool complete,
-                                bool no_query_text_needed,
+                                bool prefer_keyword,

[Peter Kasting, 2011/01/25 23:20:44]

Nit: Super minor, but it might be better to swap |prefer_keyword| and
|support_replacement| as that groups together the flags about the keyword itself
and then the flags about the current autocomplete system state.

[James Su, 2011/01/26 00:53:31]

Done.

+                                bool support_replacement,
                                 bool allow_exact_keyword_match);
 
   // Creates a fully marked-up AutocompleteMatch from the user's input.