summaryrefslogtreecommitdiffstats
path: root/rlz/OWNERS
diff options
context:
space:
mode:
authormpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-06-22 20:30:35 +0000
committermpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-06-22 20:30:35 +0000
commit128dc6ce74fe2c677e3d302e7ff10cc7e3e3e7ae (patch)
treed6f76b347cdac720aef118680b26c277030c588e /rlz/OWNERS
parent636c0fbfbaa3423a2bb1c3e5bd7d897e598fdb44 (diff)
downloadchromium_src-128dc6ce74fe2c677e3d302e7ff10cc7e3e3e7ae.zip
chromium_src-128dc6ce74fe2c677e3d302e7ff10cc7e3e3e7ae.tar.gz
chromium_src-128dc6ce74fe2c677e3d302e7ff10cc7e3e3e7ae.tar.bz2
Omnibox: Allow HistoryQuickProvider to Reorder Results for Inlining
Currently, if the best HistoryQuickProvider suggestion isn't inlineable, all HistoryQuickProvider suggestions get demoted to non-inlineable scores. This keeps them in relevance order. This change adds a parameter to alter this behavior. The new alternative behavior reorders the HistoryQuickProvider's suggestions so an inlineable one appears first (if possible), and only demotes if necessary. This parameter is enabled by a command line flag. I've also made it visible in about:flags. This change is not yet ready for a field trial. (I think a field trial would be negative until we tune scoring more.) BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/10532186 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143697 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'rlz/OWNERS')
0 files changed, 0 insertions, 0 deletions