Status: Assigned Owner: [email protected] Labels: Type-Bug Pri-3 OS-All Area-BrowserUI
New issue 6905 by [email protected]: HistoryAutocomplete should score typed versus untyped exact matches differently http://code.google.com/p/chromium/issues/detail?id=6905 If I have visited a link to a URL like "b" which, when typed, would look like an UNKNOWN input type, but I've never _typed_ that URL, then what happens when the user types this and presses enter depends on whether the popup is open and how fast they press enter. That's because the untyped result comes back asynchronously but is scored higher than the synchronously available Google search result for this text. After some thought, I think making the scoring like: exact (typed) > Google > exact (untyped) ...fixes this case and works best. The only other option is to force autocomplete to always run to the point where all asynchronous results which could return a higher score than the best synchronous result have completed. I don't even know how to accomplish that, and it would certainly be slow. -- 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 -~----------~----~----~----~------~----~------~--~---
