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

Having implemented a web scraper, I have actually seen one-slash and triple-slash URLs in the wild (a lot of the time, they're from posts on social media, but we've seen news content from popular sources contain such URLs as well. Part of the reason you never notice is that the simply browsers handle this silently.). Additionally, there is plenty of popular syntax not supported by most URL parsing libraries, like the `"//example.com/"` syntax to keep a relative scheme. We've also encountered a lot of links that use Unicode characters directly inline.

A specification to implement the web as seen by browsers is invaluable to us, since otherwise it's been hacks and guesswork to get right.

---
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-218523334