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

> Unintuitive error-handling behavior

It might be intuitive that 3 slashes in `http:///example.org/` would result in failure, but for web compat the parser needs to not return failure. If the syntax section were to match what the parser accepts, it would mean that 3 slashes is not a syntax violation, and so conformance checkers would not give any error message when people accidentally use too many slashes.

> Errors involving known interoperability problems in legacy user agents

Converting backslashes to forward slashes in URLs is an example where there wasn't interoperability in legacy user agents, but doing so gives better compatibility with web content. If the syntax section were to match what the parser accepts, conformance checkers would not give any error message when people accidentally use backward slashes, and the URLs would not work in some legacy user agents.

And so on. Making them different is the entire point; it is required to have an effect at all.

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