Re: [whatwg/url] Host parsing UTF-8 decoding can fail (#215)

I didn't add tests on WPT yet, but the two tests from my patch, "http://example.com%A0" and "http://%E2%98%83", would be great to add.
My test format is kind of confusing.  The first row with empty values (and the original string for things like the anchor tag that need the original invalid URL) indicates that parsing failed with "http://example.com%A0", which now makes WebKit match Chrome and Firefox.  The second row shows WebKit's old behavior, which would just make the A lowercase.  Same with "http://%E2%98%83" parsing now to the punycode-encoded Unicode snowman, "xn--n3h", where old WebKit's behavior would just leave it as "%e2%98%83"

-- 
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/215#issuecomment-274731747