Not only that. We would have issues with it looking like a samba url.
What issues would those be? I've been using //-links for a while now without any problems.
What comes to the commit message, it is not just Firefox, and it is not just http, but the protocol the page was served in.
This is a "network-path reference", see RFC 3986 section 4.2: http://tools.ietf.org/html/rfc3986#section-4.2. //foo resolves to http://foo if the current page is HTTP, https://foo if it's HTTPS, file://foo if it's a local file, etc. It's supported consistently by all browsers AFAIK. If we ever get HTTPS working at the same URLs as HTTP, we'll probably switch all internal URLs to start with // instead of http://, so that we can serve the same HTML pages to HTTP and HTTPS users.
I can't wait to see how creatively Code Review mangles this post.
Not mangled at all, thankfully.
That would be bug 20342 :)