Enable Better Omnibox History Matching Arrives in About:Flags

Posted on 25. Feb, 2011 by in Features, Tips

flattr this!

Along with the recently changed “about:flags” Omnibox UI, a new experimental feature has come to the newest builds of Chromium. It’s called Enable Better Omnibox History Matching, and we’re going to suspect that the description is fitting enough when it says “enables substring and multi-fragment matching within URLs from history”.

omniboxhistorymatch
Judging by this Chromium bug report, there have been issues with the Omnibox not returning the right results. It looks like for some users whenever they enter in some terms the box returns Google Search results over history. That’s probably because if you just enter in a few letters of a query, the Instant Search just kicks in as opposed to looking through your history.

Despite some recent talk about UI changes, I still think that Google wants to make the Omnibox, well, omnipresent. In order to do that, it needs to be able to look up history as well as search queries and find that balance somewhere in between. What would really be useful is if there were an operator to specifically search for history, which I’m sure will come at some point. Or perhaps more likely is that there will be an extension.

historyomnibox
Of course, you can always go to “chrome://history” and search, but then you’re not getting the best of everything by being able to use the Omnibox. How do you think Google can better incorporate your own browsing history? Have you found a trick to doing so?

  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite
  • services sprite

Tags: , , , , , ,

6 Responses to “Enable Better Omnibox History Matching Arrives in About:Flags”

  1. [...] thechromesource [...]

  2. [...] http://www.thechromesource.com Partager / [...]

  3. [...] via thechromesource [...]

  4. A340-600

    27. Feb, 2011

    Sounds good. I’m not a big fan of search through my browsing history in the Omnibox. It can be a hit and miss when searching browsing history on the Omnibox.

  5. [...] via:TheChromeSource 编/译:谷饭 [...]

  6. [...] an undesired result. This may be because of bad history matching, which was actually suppposed to be addressed in another experimental feature. It is also possible that nonessential URLs were just popping up in the Instant queue – ever [...]

Leave a Reply

Name

Email

Website

Comment