diff options
| author | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-04 14:45:53 +0000 |
|---|---|---|
| committer | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-04 14:45:53 +0000 |
| commit | 7ad2295c2db5b7001e869a3ec9ed62a7086aaea8 (patch) | |
| tree | 422b069f4baa55dff7504ab59c5088866221ce44 /content/browser/renderer_host/test_render_view_host.cc | |
| parent | 09a40196dc0cdd4c9315fff4d08d5e5934dd25e0 (diff) | |
| download | chromium_src-7ad2295c2db5b7001e869a3ec9ed62a7086aaea8.zip chromium_src-7ad2295c2db5b7001e869a3ec9ed62a7086aaea8.tar.gz chromium_src-7ad2295c2db5b7001e869a3ec9ed62a7086aaea8.tar.bz2 | |
Changes the HistoryURLProvider such that if the first pass produced an
inline autocomplete match we don't attempt to fixup the 'what you typed
match' in the second pass. The problem scenario is a url you've typed
like 'pandora.com' and a url you haven't typed, like 'p'. If this
happens, the first pass produces 'pandora.com' with a relevancy of
1400, but the second pass produce 'p' with 1200, and
'pandora.com' would get a much lower relevancy. If the SearchProvider
also provided an inline autocomplete match > 1200, then the omnibox
flickers between the results.
TEST=covered by unit test
BUG=77677
R=pkasting@chromium.org
Review URL: http://codereview.chromium.org/6749039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80311 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/renderer_host/test_render_view_host.cc')
0 files changed, 0 insertions, 0 deletions