- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 19 Dec 2016 10:36:03 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 19 December 2016 18:36:34 UTC
OK, added a number of my favorite examples. There were certainly more (e.g. demonstrating some of the host normalization like IDNA and IPv4/v6 parsing would have been cool; demonstrating file URLs would probably help) but this I think hammers home the main points about how a large variety of weird URLs cam parse, but some things can still cause failure. Regarding validity. I think the current location is pretty good. Maybe what we need is a paragraph spelling out the fact that URL syntax is all about validity, and what validity means in practice. That paragraph could link to this example, perhaps. Adding a column for validity seems OK but we might need some more valid examples in that case, as I emphasized the invalid ones. Also I'm not sure it applies that well since we talk about validity on an absolute URL, not on an input to the URL parser, right? So e.g. the row that lists `example` + `https://example.com/demo` would not work out great, would it? -- 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/pull/177#issuecomment-268041816
Received on Monday, 19 December 2016 18:36:34 UTC