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 419594
To read all comments associated with this story, please click here.
What about port numbers?
by raboof on Sun 18th Apr 2010 13:44 UTC
Member since:

When visiting a http site, the port number is usually ':80' - you can specify another one if you wish, but if you leave it out it'll be ':80'.

It makes sense to do the same for the protocol in a web address: you can specify another one, but it'll usually be 'http://', so in that case it doesn't have to be shown.

The only inelegant part is that http and https are both common. OTOH, it's quite rare these days to have the *same* site available both secured and unsecured - usually the unsecured url just redirects to the secured version - so we can hide both 'http' and 'https' and use the 'lock' icon to show the difference.

Reply Score: 4

RE: What about port numbers?
by btrimby on Sun 18th Apr 2010 14:58 in reply to "What about port numbers?"
btrimby Member since:

I prefer consistency to hiding things that are sometimes unnecessary. But I'm just one of those crazy people who have actually used the browser with the "feature" in question and notice it as "something wrong" according to my eye.

Reply Parent Score: 1

RE[2]: What about port numbers?
by raboof on Sun 18th Apr 2010 15:30 in reply to "RE: What about port numbers?"
raboof Member since:

I prefer consistency

Consistency is hardly ever a black-and-white thing though: for example, one could argue that hiding the port number when it's not 80 is also 'inconsistent' - however I don't think anyone would propose to always show it ;) .

Reply Parent Score: 2