Comment #9 on issue 9732 by [email protected]: Fallback to site-search for URLs without Tab-to-search http://code.google.com/p/chromium/issues/detail?id=9732
<tab> generally moves among dropdown items in other browsers. We're already defying that convention. It sounds like to implement comment 6, we'd need a "best engine for input" that would return, in order: * A keyword exactly matching the user's input * A keyword exactly matching the first whitespace-delimited token of the autocompleted string * If the string is a URL: * With scheme and "www." stripped off of both keyword and string, the keyword which matches the longest prefix of the string, such that after the match is a component delimiter (or the end of the string) * If the user's default search engine is Google (?), site-search on the URL's hostname Notes: * The craziness on that "longest prefix" item is so we can later do things like having different entries for amazon.com/foo and amazon.com/bar * The restriction on "user's default search engine is Google" is to avoid using Google for anything when users didn't want it used as the search engine. Alternatives are to use it anyway (probably will irritate some users) or to define a "site restrict keyword" for other engines (a big hassle to investigate). Finally, we should consider having the site-search query be an "I'm Feeling Lucky" query so the user winds up on the desired site if possible, and doesn't see a (surprising) Google search result page. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
