3 ms·

That's definitely something that's kept me from adopting Chrome full time. A lot of people grouse about the AwesomeBar, but the Omnibox has taken a very long t

That's definitely something that's kept me from adopting Chrome full time. A lot of people grouse about the AwesomeBar, but the Omnibox has taken a very long time to achieve feature parity, and still isn't there yet. Using the AwesomeBar is my preferred mode of searching through my history for things I half-remember reading, and it usually more convenient than either the Omnibox or Safari's history full text search. That said, even the dev channel release of Chrome still doesn't get this right. If I want to go to the ESPN NFC East blog (http://espn.go.com/blog/nfceast http://espn.go.com/blog/nfceast), I usually type "nfcea" into the AwesomeBar and it pops up as the first result. The Omnibox suggests searching for "nfc east blog" but doesn't show the appropriate URL from my history.

abraham 15y ago
I did a little experimenting on the dev channel. I found that after visiting http://espn.go.com/blog/nfceast http://espn.go.com/blog/nfceast once typing nfc would suggest it and this HN post and nfc through nfceast would suggest this HN page.
- Perceval 15y ago
  Doesn't work for me for whatever reason. Oddly, it will show the google search for "nfc east blog" from my history (www.google.com/search?aq=1&oq=nfceast&sourceid=chrome&ie=UTF-8&q=nfc+east+blog), but it won't show the actual blog url. Maddening.
paulirish 15y ago
There are always a few experiments related to the omnibox in about:flags that you can try out to see where things may be headed.
- Perceval 15y ago
  Thanks, I enabled 'shortcuts' in the omnibox. We'll see if that improves my results.
Jarred 15y ago
This bothers me actually. When I start to type "facebook", it goes to "about:flags". It should have an additional check if the user doesn't end up picking what was autocompleted for them, then it puts back what the user originally typed. That way this feature can be used without frustrating the user.

abraham 15y ago

I did a little experimenting on the dev channel. I found that after visiting http://espn.go.com/blog/nfceast http://espn.go.com/blog/nfceast once typing nfc would suggest it and this HN post and nfc through nfceast would suggest this HN page.

Perceval 15y ago
Doesn't work for me for whatever reason. Oddly, it will show the google search for "nfc east blog" from my history (www.google.com/search?aq=1&oq=nfceast&sourceid=chrome&ie=UTF-8&q=nfc+east+blog), but it won't show the actual blog url. Maddening.

paulirish 15y ago

There are always a few experiments related to the omnibox in about:flags that you can try out to see where things may be headed.

Perceval 15y ago
Thanks, I enabled 'shortcuts' in the omnibox. We'll see if that improves my results.

Jarred 15y ago

This bothers me actually. When I start to type "facebook", it goes to "about:flags". It should have an additional check if the user doesn't end up picking what was autocompleted for them, then it puts back what the user originally typed. That way this feature can be used without frustrating the user.