That's an interesting opposing view; because the thing that hooked me on Chrome was the address bar. I can no longer function efficiently in other browsers because, for me anyway, it is so streamlined.
Same thing for me. The possibility to integrate search engines (or other forms) with a keyword is what keeps me in Chrome. I have to agree though that FFs autocomplete feature is better. Chrome only seems to match addresses if you type their beginning.
Firefox has also had this feature for a while, right click > 'Add a Keyword for this Search' which is indispensable.
That's an interesting opposing view; because the thing that hooked me on Chrome was the address bar. I can no longer function efficiently in other browsers because, for me anyway, it is so streamlined.
Same thing for me. The possibility to integrate search engines (or other forms) with a keyword is what keeps me in Chrome. I have to agree though that FFs autocomplete feature is better. Chrome only seems to match addresses if you type their beginning.
Firefox has also had this feature for a while, right click > 'Add a Keyword for this Search' which is indispensable.
does it have firebug yet? That's all I care about. And no, the development toolbar is not good enough
I'd have to say the developer tools are comparable to Firebug and won't freeze Chrome the way Firebug periodically freezes Firefox.
You, my friend, clearly don't use Firebug that much. Until you can add new attributes to existing selectors in developer tools, it simply cannot compare
I'm not sure how Chrome's treatment of custom search engines differs from Firefox's. In Chrome, you can associate a URL with a keyword so that when you type "keyword query" into the address bar, the %s parameter in the associated URL is replaced with your query. In what way is Firefox's better?
In Firefox, I can type any of the following into the awesome bar: "d victual" -> looks up "victual" "j joust" -> gets "joust" in a Japanese dictionary "wp Boron" -> displays the wikipedia page "Boron" "hn patio11" -> displays HN comments of "patio11" How can I do this in Chrome? Last time I checked, it wasn't possible. If it is now, then I might start using Chrome for more resource intensive flash games.
Go into your search engine manager (via options or the omnibox's context menu) and edit the keywords for your chosen engine - note that we automatically add engines here with the keyword as the domain, so if you do a search on amazon.com, we'll automatically add amazon with the keyword 'amazon.com' - with autocomplete, this lets you type 'am', then press tab to search (or space-separate the keywork from the term).
I'm not sure how Chrome's treatment of custom search engines differs from Firefox's. In Chrome, you can associate a URL with a keyword so that when you type "keyword query" into the address bar, the %s parameter in the associated URL is replaced with your query. In what way is Firefox's better?
In Firefox, I can type any of the following into the awesome bar: "d victual" -> looks up "victual" "j joust" -> gets "joust" in a Japanese dictionary "wp Boron" -> displays the wikipedia page "Boron" "hn patio11" -> displays HN comments of "patio11" How can I do this in Chrome? Last time I checked, it wasn't possible. If it is now, then I might start using Chrome for more resource intensive flash games.
You can do the same in Chrome. Check under Options ("Basic" tab) > "Manage" next to Default Search. You should see a list of search engines. If you've already used the search engine and Chrome has picked it up, just select it from the list, "Edit", and customize what keyword you want to use (by default it uses the basic URL). If it's not there, "Add" to make a new one.
Probably the single thing that keeps me using Firefox is its address bar. It's a much nicer experience than Chrome's, with its user-friendly auto complete mechanisms. The speed of the browsers is rarely the bottleneck for me anymore. I'll switch to Chrome for intense javascript experiences, but that's about it. I feel like chrome needs to start focusing more time on the experience - these speed improvements aren't pa…
I think we can all agree that Safari is the furthest behind in this regard. For a company that takes pride in stripping things down to the bare essentials, having an address bar and a search bar is becoming obnoxious.
One small thing I like about Safari is that it understands addresses like nytimes/politics as nytimes.com/politics.
Probably the single thing that keeps me using Firefox is its address bar. It's a much nicer experience than Chrome's, with its user-friendly auto complete mechanisms. The speed of the browsers is rarely the bottleneck for me anymore. I'll switch to Chrome for intense javascript experiences, but that's about it. I feel like chrome needs to start focusing more time on the experience - these speed improvements aren't pa…
I think we can all agree that Safari is the furthest behind in this regard. For a company that takes pride in stripping things down to the bare essentials, having an address bar and a search bar is becoming obnoxious.
I guess that's true. Personally I guess I never noticed because I have Quicksilver indexing my Safari history. I can also use it to do all my Web searches.
For everyone asking what's wrong with Chrome's URL bar, here's one specific example I run into. I go visit Google Analytics relative often. In Firefox, I can start typing analytics.. and it pulls up GA as an option very quickly. With chrome it never shows up at all, instead I have to start typing google, and it'll show up as the 3rd or 4th option. It's hard to remember all the specific annoyances, but this is one of…
I suspect this is either a product of what is familiar to individuals or of different browsers suiting different surfing styles. For me FF never seems to pull up Google analytics for "analytics" but I only have to get to "anal"[1] before it appears as #1 in Chrome. The algorithms probably train better for different people 1. There is probably some ironic joke in there somewhere :)
I suspect it's a matter of time, at least for Firefox if not for Chrome. Firefox's is mainly frequency based, so it needs a little while to train.
It took 2-3 weeks for FF's bar to really start to get awesome for me.