diff options
| author | mpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-12-05 20:26:02 +0000 |
|---|---|---|
| committer | mpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-12-05 20:26:02 +0000 |
| commit | c1bf78e353678cd033daaa23279db5199f9a1040 (patch) | |
| tree | 856250458780aa39fa611e63a523a4e379bba4e2 /chrome/browser/icon_manager.h | |
| parent | 2ee3da9d6c75aa8633fa2458891eeb91d1632db3 (diff) | |
| download | chromium_src-c1bf78e353678cd033daaa23279db5199f9a1040.zip chromium_src-c1bf78e353678cd033daaa23279db5199f9a1040.tar.gz chromium_src-c1bf78e353678cd033daaa23279db5199f9a1040.tar.bz2 | |
Omnibox: Revise HistoryQuickProvider Code for URL-What-You-Typed Goes First
I noticed that the code in HQP to guarantee thatURL-what-you-typed goes first (when it's available) is too aggressive. For instance, when URL-what-you-typed is a visited URL, it gets a score of 1413 currently. But HQP makes the scores of its results <1200. This means that other provider's results (such as search suggestions) can sneak in in the middle. In this example, after this change HQP realizes the URL-what-you-typed result will have score 1413, and so it simply makes sure its results have scores less than 1413.
This is a step in making HQP be able to replace HUP.
In the process of making this change, I had to expose HUP's relevancy scores. I made them a public static const int.
I know these scores are used in scored_history_match in HUP-like-scoring mode. Hence I changed the code in scored_history_match to use these newly exposed constants.
BUG=
TEST=by hand
Review URL: https://chromiumcodereview.appspot.com/11415265
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171295 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/icon_manager.h')
0 files changed, 0 insertions, 0 deletions