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

@SEAPUNK
If the purpose of the specification is to sync web browser implementations in incrementally becoming less permissive, then:
* The spec should say that, and not claim to define URLs, domain names and IP addresses.
* The spec should not claim to be a replacement of the RFCs.
* The spec shouldn't be trying to change the terminology from "URI" to "URL".
* The spec should only concern browsers and should mention explicitly that it is not relevant for tools like curl, libraries that parse URLs, IRC clients and so on.
* Browsers that are already stricter should not be expected to implement the spec, since they'd need to revert those changes right after when the spec incrementally becomes less permissive.

So the spec would be about coordinating the efforts for making Firefox, Chrome and Edge progressively stricter and getting them as close to the RFCs as possible. (How close it is possible to bring them would depend on how many web pages have incorrect URLs.)

Now, that'd be an initiative I can agree with, and a plan I would find reasonable.

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