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 419624
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: What about port numbers?
by btrimby on Sun 18th Apr 2010 16:31 UTC in reply to "RE[2]: What about port numbers?"
Member since:

Hiding the port number is done when it is the default port number for the scheme. I regularly use alternate port numbers on a daily basis, and it'd actually make *my* life easier if I could always see the port. I'll not bother to argue that that should be changed though. It's too late for that.

I see how you parallel the hiding of the "default scheme" and that's a fairly rational argument, but there is a factor of time involved, in the time that it's been around that will make changes like this controversial.

Someone else commented about the length of addresses and such, and that it was good to see more information. Well, even if most would consider this information unnecessary, it is information, and it is being hidden. Currently, the way the chromium devs implemented it, you can't always see the full URI without pasting it. The same thing with the port, really. I'd actually like an option in browsers to show the scheme and port no matter what.

I like the other things Chromium has started doing, such as a red skull and crossbones for self-signed sites, but I prefer to see as much explicit information as possible.

Reply Parent Score: 2