Better handling of UNKNOWN versus QUERY in a couple ways....

Better handling of UNKNOWN versus QUERY in a couple ways.

First, made it possible to navigate to "invalid" hostnames in a number of additional cases, including when the user types an explicit scheme or when we have a valid TLD and no spaces.  The default action for these kinds of inputs is still search, but we'll pull up an accidental search infobar if need be now.

Second, made the HistoryURLProvider show a What You Typed match for UNKNOWN inputs when the user explicitly typed "http:" or "https:" at the front, since these have the highest probability of being navigational inputs.

BUG=26341
TEST=Type "http://foo bar baz.com" and verify you are given a (non-default) entry in the dropdown to navigate.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=30830

[brettw, 2009-11-03 03:30:22]

LGTM

http://codereview.chromium.org/353010/diff/1/5
File chrome/browser/autocomplete/autocomplete_unittest.cc (right):

http://codereview.chromium.org/353010/diff/1/5#newcode221
Line 221: { L"foo+bar", AutocompleteInput::QUERY },
Can you add "foo+bar.com"? It would make it a little more clear how this diffes
from "foo+bar"