http://mashable.com/2010/04/19/google-chrome-ditches-http/

<<When you see some text prefixed by “Http://”, you automatically assume that what follows is a web address, as defined by the Hypertext Transfer Protocol. The question is, since most web addresses are easily recognizable anyway, do you really need it?

The developers of Google Chrome don’t think you do>>

This slightly confused me the other day. I wanted to copy and paste the web address, saw there wasn't the http:// so typed it before pasting the address. Turns out it copys the http:// even though it's not there!

https:// does still appear (for obvious reasons)

I'm finding it a bit weird not having it there :/

I noticied that this Sunday too, that sucks!

"The question is, since most web addresses are easily recognizable anyway, do you really need it?"
sure, when I access to http://localhost , "localhost" isn't a such recognizable web address...

I've set my localhost up as a shortcut, so now i just type 'lh' and it navigates there. I like this change.

The change seems to make sense in terms of minimalism, though I'd like to give it a try before seeing if it really works well in day to day browsing (I suppose exceptions, like https, will still show in the URL?). As for accessing localhost, Tom can you explain what problem appears for you?

There is also an option to add credit cards under the button AutoFill profiles which is also new compared to the stable version.

Anyone [but me] remembers pre-www attempts at simplifying Unix* syntax of fetching remote documents? The one-line url (with "locator" later replaced by "identifier" in "uri") comprising both a command and its argument is one of the two greatest inventions of Tim Berners-Lee, but there were prior samples of the same art. Gopher had some of that, but I also knew of at least three specific finger-daemons which permitted fetching files via almost url-like syntax; e.g.

$> finger doc=docname%userhost.domain

In any event, the "http" (always lower case!) DEFAULT SCHEME token should have been dropped ages ago, at the same time when the powwwers that be decided that the leading "www" in urls was superfluous. That token –which, apart from everything else, was a dog to spell out in English – originally was adopted to let remote servers route any ongoing access to its intended server-port ("ftp" vs. "www" vs. "telnet," etc, which were aliased locally) soon outgrew its usefulness as hostmaters and newly-minted webmasters realized they had to provide as much local-aliasing redundancy as they could stomach (thus e.g. "http://ftp" acting as were it "ftp://ftp" – just as "server" and "www.server" resolved the same).

In any event, good move by the Chrome team, esp. with implementing the transparent hack that makes copying location field return the uri complete with the leading scheme token.