Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367

Comment #7 by [EMAIL PROTECTED]:
There are far too many disparate requests in the comments on this bug.   
Please keep
bugs to one issue.

I believe most of what's being requested here is some form of machine  
learning that
will match input strings to result URLs.  The Awesome Bar does this, the  
Omnibox does
not.  This is worth investigation, we've talked about it off and on for a  
good year
or so.

There are other issues above:
* We do, actually, sort by visit frequency -- or more specifically typed  
frequency
(since the Omnibox is an accelerator for typing) and then visit frequency.
* Displaying more results has tradeoffs.  We may end up experimenting  
here.  There
are a lot of subtle issues.
* Wheel scroll through results only makes sense if we actually have a  
scrollbar,
which we don't right now.  If we did, then we would certainly want to  
support
something like this.
* Poor matching inside URL components is an artifact of how we're doing the  
queries
to locate these matches.  We've traded accuracy and depth away for speed  
here.  Long
tem I'd like to find a solution that lets us get better results, on the  
level of the
Awesome Bar, but in the short term it has not been clear how to achieve that
_quickly_.  Speed is a guiding design principle of the Omnibox.


Issue attribute updates:
        Summary: Machine learning for omnibox (match input strings to result 
URLs)
        Status: Untriaged
        Labels: -Pri-2 Pri-3

-- 
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

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to