Comment #25 on issue 367 by phajdan...@chromium.org: Machine learning for
omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Issue 3082 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fiel
Comment #24 on issue 367 by mahaniok: Machine learning for omnibox (match
input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
We could use the data on how long the person stayed on the site suggested.
Example problem:
I have visited fahrplan.zvv.ch and fahrpla
Comment #23 on issue 367 by phajdan...@chromium.org: Machine learning for
omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Issue 7295 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fiel
Comment #21 on issue 367 by sheri...@shezza.org: Machine learning for
omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
"Power is nothing without control" :)
--
You received this message because you are listed in the owner
or CC fields of this
Comment #20 on issue 367 by almunav: Machine learning for omnibox (match
input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
@pkasting
you could be here all day long explaining how the omnibar was designed for
speed but
it doesn't change the fact that omnibar
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #19 by g.teunis:
Sorry but how can this be status unconfirmed?
I see lots of people agreeing here, even from people of chromium itself?
Please revert the st
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #18 by [EMAIL PROTECTED]:
Issue attribute updates:
Status: Unconfirmed
Labels: Mstone-X
--
You received this message because you are li
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #17 by g.teunis:
I do not agree with comment 16.
What I would like is the following.
Remove all "search google for " and root urls from search results
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #16 by lealcy:
I prefer omnibar show the root url first, so before it show the other urls.
--
You received this message because you are listed in the own
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #14 by g.teunis:
Firefox does a really good job here. There might be a small performance
penalty but I
think it will really improve the omnibar if we copie
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #13 by [EMAIL PROTECTED]:
Gah, that last post was (obviously) by me
--
You received this message because you are listed in the owner
or CC fields of this
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #12 by zerodpx:
I was trying to make clear that visiting a Google search result page does
not count
as typing in the address of the front page of Google, b
Issue 367: Machine learning for omnibox (match input strings to result URLs)
http://code.google.com/p/chromium/issues/detail?id=367
Comment #11 by sadlittleboy:
Except that I specifically said I had NOT typed in those pages more often.
I typed
each in once. (and probably reloaded once or twice
13 matches
Mail list logo
