remove need for "//" after protocol?

[stevenvachon]

If you remember this: http://bits.blogs.nytimes.com/2009/10/12/the-webs-inventor-regrets-one-small-thing/?_r=0

[annevk]

We cannot make backwards-incompatible changes.

[stevenvachon]

Would it still be backwards-incompatible if the "//" were optional instead of required?

[annevk]

The problem is that the parsing of such URLs depends on what the base URL is. Better to keep requiring it.

[stevenvachon]

If the base URL has it, then the resolved URL can as well. It could optionally not do so too, I would think, but that may be something for a URL minifier/optimizer library.

[annevk]

I think you might have missed my point. I recommend looking at https://url.spec.whatwg.org/#example-url-parsing. Contrast examples 1, 4, and 5 in that table.

[stevenvachon]

The 4th in that table might pose a problem.

There're other related examples not listed in that table:

Input	Base	Output
https:example		https://example/
https:example	https://example.com	https://example/

[annevk]

The first is 1, no? The second looks bogus. Should be https://example.com/example.

[stevenvachon]

The first one in your table has both a domain and top-level domain, which shouldn't make a difference.

Both whatwg-url and Node v7's url.URL must have the second one (in my example) wrong, then.

Input	Base	Output
https:example		https://example/
https:example	http://example.com	https://example/

[stevenvachon]

(updated above comment)