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

> Standards that do not reflect running code are not valuable

Running code will often have bugs, bad behavior, and plan illogical choices. The purpose of a standard is to *specify* what those bugs/bad behaviors *actually are* so they can be fixed.

Writing a standard that accepts everything means it's not a standard at all. It's just throwing it's hands up and saying "well, they do what they want anyhow, may as well say it's ok."

It's especially frustrating in this specific case because that's not even a good justification (as illustrated: several major browsers, and the largest mobile browser, *specifically don't allow this behavior*).

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