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

> Safari supports more than 2 slashes, but not from the location bar

> Well cURL supports more than 2 slashes, and has other RFC deviations for the very reason that RFC don't actually reflect the real world.

So, it’s not the same everywhere. Useful standard then. I thought a standard is defined as a format that is guaranteed to work everywhere.

> And what happens if you do window.location = "http://///////google.com/";?

That wasn’t the question, the question was if you can invoke it from any other app. And that requires going through the intent system, which uses Java’s URL parser, and heavily differs depending on Android version – on over 90% of devices, you get a MalformedURLException.

> The Web has a URL interface exposed to JavaScript that requires following this Standard. That ship sailed a long ago and this will never be renamed (that would break webcompat).

And in return, it’s better to break the URL standard and the entire ecosystem around it?

If you define a standard, I expect that I can take any data conforming to this standard, and use it *everywhere*. This is not the case with this URL standard. Therefore it is broken.

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