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

A URL can be defined to only have two slashed but the spec mandate that parsers should handle thousands the same way the IETF standard can say that URL producers should not create percent-encoded octets for the ALPHA range, but URL consumers should decode them nonetheless.

https://tools.ietf.org/html/rfc3986#section-2.3
> For consistency, percent-encoded octets in the ranges of ALPHA (%41-%5A and %61-%7A), DIGIT (%30-%39), hyphen (%2D), period (%2E), underscore (%5F), or tilde (%7E) should not be created by URI producers and, when found in a URI, should be decoded to their corresponding unreserved characters by URI normalizers.

I'll concede that it just says "should not" and not "SHOULD NOT", but that's pretty similar in spirit in my book.

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