Issue 3633: Need to solve the tab-to-search-expiring bug http://code.google.com/p/chromium/issues/detail?id=3633
Comment #8 by [EMAIL PROTECTED]: I did lots of thinking about this last night and this morning. The right fix is trickier than I thought, but I think possible. First, we should change the scoring function on the keyword provider to score keywords highly when their frequency (or perhaps frecency?) is high (logarithmic function?). This should be tuned against the history URL provider's function (which may also need to become more flexible) such that good keywords beat out bad inline autocompletions. Next, when the controller sees that one of these keywords is the best result (and the keyword UI won't be showing?), it should create a match corresponding to what would happen if the user hit enter on the fill_into_edit text from that match, and then insert it into the result set just above the keyword match. The result of this is that oft-used keywords, whether they're auto or manual, will propagate to the top of the list, but the user will still get consistent behavior if he happens to hit <enter> instead of <tab>. -- 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 -~----------~----~----~----~------~----~------~--~---
