diff options
| author | mpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-27 09:24:46 +0000 |
|---|---|---|
| committer | mpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-27 09:24:46 +0000 |
| commit | d519d39a623ff08da101e6f0fd7e633e10b7f0f6 (patch) | |
| tree | 105ceb9cda10f23b24f9c045053622779158505e /media/audio | |
| parent | 3da4116d18cfc649e34c23c1f3db645c1faf32dc (diff) | |
| download | chromium_src-d519d39a623ff08da101e6f0fd7e633e10b7f0f6.zip chromium_src-d519d39a623ff08da101e6f0fd7e633e10b7f0f6.tar.gz chromium_src-d519d39a623ff08da101e6f0fd7e633e10b7f0f6.tar.bz2 | |
Omnibox: Don't Allow Navsuggestions in Keyword Mode
In keyword mode, demote all navsuggestion results below the best ranking
keyword query mode. This is necessary so a navsuggestion doesn't appear
inline, which would end up kicking the user out of keyword mode.
This has to be done in SearchProvider. It cannot be done on the suggest server side because the suggest server does not know whether it is serving results to a default search engine or a keyword search engine.
Note: there can be bad cases when the default search engine and the keyword
search engine both supply relevance scores. I haven't thought those these
issues yet as we only know of one engine that supplies scores at this
time. (And if the same engine is used for the default and keyword search
engine then it's only queried once, so these concerns don't apply.)
BUG=196550
Review URL: https://chromiumcodereview.appspot.com/13031006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@190886 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'media/audio')
0 files changed, 0 insertions, 0 deletions