Linked by Thom Holwerda on Sun 18th Apr 2010 11:57 UTC, submitted by Anonymous
Google Now this is something that I find really interesting. We all know and love Google Chrome/Chromium (and if you don't, you're demonstrably wrong), but Google recently made a change in the developer version that ruffled some feathers: the URL field will no longer show the "http://". This made a lot of people very upset.
Thread beginning with comment 419670
To read all comments associated with this story, please click here.
Combined Search and Address Bar
by The1stImmortal on Sun 18th Apr 2010 23:17 UTC
The1stImmortal
Member since:
2005-10-20

Personally, this bothers me because Chrome doesn't have independent search and address fields. I like to use the schema part to force chrome (or at least feel like I'm forcing chrome) to treat something as an address, not a search term. This can be especially handy for internal, private domains (I know a case or two where the default site at domain name "intranet" takes them to their intranet - in chrome this is just as likely to search for "intranet" as to go to http://intranet/)

Were the Chrome address bar to be *exclusively* for addresses, then this would be OK with me, but with it doubling as a search bar, it's potentially ambiguous. If the address bar were exclusively for addresses, then displaying merely the domain there wouldn't be confusing. Search terms would be displayed in the search bar. But with a combined field, does showing say "example.com" in the address/search bar mean you're AT example.com, or you've SEARCHED for example.com?

It's good to blur the line between search and direct addressing (and of course heavily in Google's interest to do so) but it shouldn't be blurred to much - to the point where it's nearly impossible to define which you're using.

Reply Score: 1