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 419589
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Hiding complexity?
by Doc Pain on Sun 18th Apr 2010 12:57 UTC in reply to "RE: Hiding complexity?"
Doc Pain
Member since:
2006-10-08

I am with this PoV.


Partially, I am, too. I may explain this.

What are they to be always displayed ? Most of sites are http/https, so removing this and adding a key icon to precise https sites is better.


I would rather prefer a static setting through the browser setup - the advantage is obvious: Because the default is OFF, average users aren't bothered. Advanced users know how to switch schema display to ON, so if they intendedly require it, they know where to do it.

As it has additionally been explained in the linked "bug discussion", copying the URI from the input field will include the schema, so it's easy to transfer the URI from the browser to somewhere else maintaining full standard compliance - and standard is to keep the schema. (The importance to keep the schema with the URI is that the schema is an essential part of the URI, and often programs decide on what specific mechanism to use in combination with a certain schema - remember, there's more than just HTTP and FTP.)

By the way, have you noticed that the example in the "bug discussion" is shortened to "www.google.com/" - you see the closing slash. Why hasn't this been removed, too? (Of course I know what it indicates, but does the average user know - or need to know?) That's a bit confusing. In cases where the default is taken, more shortening is possible, up to "www.google.com" - no schema, no slash.

As you said, boulabiar: Most sites are HTTP anyway. If you use the browser to browse something else, for example a FTP directory, the default should be to display the ftp:// schema anyway, regardless of the setting, just to make sure there's no confusion.

In most cases, the address bar is not for entering information, it's mostly to show "where you are", and given the fact you're using a web browser, you're on a web site, so http:// is the most common schema for this. Or tell me: When have you seen someone entering an URI manually, including the schema?

Even if most advanced users won't like this chance, they will be able to live with it. As I am not a Google Chrome / Chromium advanced user (I still prefer Opera) advanced user, it even doesn't matter to me, so let the developers have their change. :-)

Reply Parent Score: 2

RE[3]: Hiding complexity?
by btrimby on Sun 18th Apr 2010 14:38 in reply to "RE[2]: Hiding complexity?"
btrimby Member since:
2009-09-30

I have seen people meticulously type in addresses, including the "http://", and I think they may start wondering why "The darn computer" is removing what they type. Now, some might just ignore it after trying to re-type it a few times. But maybe they'll use another browser which doesn't have a "bug" which removes part of what they type.

(Yes, I'm aware that there are other things that get changed when you go to a website. But the http:// has usually only been changed to https:// which is accompanied by additional information)

Reply Parent Score: 1

RE[4]: Hiding complexity?
by Delgarde on Sun 18th Apr 2010 21:30 in reply to "RE[3]: Hiding complexity?"
Delgarde Member since:
2008-08-19

I have seen people meticulously type in addresses, including the "http://", and I think they may start wondering why "The darn computer" is removing what they type. Now, some might just ignore it after trying to re-type it a few times. But maybe they'll use another browser which doesn't have a "bug" which removes part of what they type.


Uh, if they can't understand what's happening, what are the odds that they have the technical knowledge to download a different browser? Or, for that matter, that they're using Chrome in the first place?

Reply Parent Score: 3