[whatwg/url] Behaviour with URIs / URNs (#289)

The spec only talks about URLs. I have a use case where resources are identified by URIs, so identifiers I receive could also be a URN. Testing in Chrome, the parser doesn't seem to break when you pass a URN:

![image](https://cloud.githubusercontent.com/assets/10532611/24577560/3fc56598-16d0-11e7-9062-80de9adf3cd1.png)

It parses `protocol` and `pathname` correctly. Is this guaranteed for all implementations? Or just happens to work in Chrome? A URN is not a URL, so I wouldn't expect a `URL` parser to necessarily parse URNs. I might even expect an implementation to throw an error.

-- 
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/289

Received on Saturday, 1 April 2017 09:49:26 UTC