Re: [whatwg/url] Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter (PR #685)

There are more failures because there are more tests, but for the part which is changed by this spec change - domains containing (raw or encoded) code points in the range `\u0000-\u0001F` or `\u007F` - Chrome passes them all.

If I changed the tests to the current spec, there would be even more failures for _all browsers_. None of them implement the current spec. WebKit was the last one, but @achristensen07 recently changed made the change to reject those code-points (for all hosts, not just domains, which is why WebKit still has one failure, but the consensus from the issue seemed to be to leave those alone for now):

> I think there is a consensus that the forbidden host code points should include all C0 controls and U+007F, and that now matches the behavior of all browsers. Let's make that change to the specification and then make a separate issue about what we want to do with opaque hosts, where there is less consensus and less spec compliance.

https://github.com/whatwg/url/issues/627#issuecomment-981906774

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/685#issuecomment-1021485540
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/pull/685/c1021485540@github.com>