Re: [whatwg/url] It's not immediately clear that "URL syntax" and "URL parser" conflict (#118)

The main difference between the WHATWG and some other standards organizations is that the [WHATWG attempts to describe the world as it is](https://wiki.whatwg.org/wiki/FAQ#What_does_.22Living_Standard.22_mean.3F), rather than as folks would like it to be. That means that if a major implementation of URLs implements them in one way, the WHATWG specification needs to allow that implementation. So, it doesn't help to "prove" that browsers are wrong by citing earlier specifications.

That said, it seems like there's a good argument to have the URL spec allow implementations to reject too many slashes, since at least one recent browser and several other tools do reject them.

---
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/118#issuecomment-218346197