Add confidence to AutocompleteMatch.

Calculated by each provider using whatever measure makes sense and stored as a float in the range [0, 1]. Will be used for determining benefit of using instant, prerender, DNS preconnect to increase success rate and avoid wasted resources.

Currently fed into UMA to validate experiment.

BUG=None
TEST=None


Review URL: http://codereview.chromium.org/7607007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@96446 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 5 insertions, 1 deletions

diff --git a/chrome/browser/autocomplete/extension_app_provider.cc b/chrome/browser/autocomplete/extension_app_provider.cc
index 0a68e8c..8fef3a5 100644
--- a/chrome/browser/autocomplete/extension_app_provider.cc
+++ b/chrome/browser/autocomplete/extension_app_provider.cc
@@ -56,7 +56,11 @@ void ExtensionAppProvider::Start(const AutocompleteInput& input,
         // We have a match, might be a partial match.
         // TODO(finnur): Figure out what type to return here, might want to have
         // the extension icon/a generic icon show up in the Omnibox.
-        AutocompleteMatch match(this, 0, false,
+        // TODO(dominich): Confidence would require us to create a match set and
+        // then iterate over to create the AutocompleteMatch objects. Currently
+        // confidence is used for instant/prerender/DNS preconnect and we may
+        // not want to do those for extension apps anyway.
+        AutocompleteMatch match(this, 0, 0.0f, false,
                                 AutocompleteMatch::EXTENSION_APP);
         match.fill_into_edit = url;
         match.destination_url = GURL(url);