[whatwg/url] Consider removing the `gopher` special-case. (#342)

`gopher` is called out as a special scheme with a default port of 70 (https://url.spec.whatwg.org/#url-miscellaneous). Browsers generally implement this bit of the spec. I'd suggest that it's time we stopped doing so.

So far as I can tell, Chrome's support for `gopher` is limited to URL parsing. The protocol itself isn't supported, and `gopher:` URLs in the address bar are treated as searches. Gecko looks like it has similar behavior.

Perhaps we could consider dropping the special-casing in URL, and just treating `gopher:` like any other scheme that the browser doesn't understand. That is, instead of parsing `gopher://hostname.goes.here` like we'd parse `http://hostname.goes.here`, we'd parse it like `not-a-scheme://hostname.goes.here`. This wouldn't preclude user agents from supporting the protocol with external handlers, of course, but it would allow them to stop pretending that they understand the scheme when they clearly don't.

WDYT, @annevk, @mcmanus, @sleevi, @travisleithead, @achristensen07?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/342