- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 30 Dec 2016 03:54:46 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 30 December 2016 11:56:17 UTC
Yeah, you are right. Even with EOF you get a path that is non-empty. Another problem here is not forbidding certain code points in the host setter. I guess I should rethink this. The other question of course is whether all this additional complexity is worth it, versus treating non-special schemes as just having a path and not being able to be base URLs for each other. (Which is what most browsers implement at the moment.) -- 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/185#issuecomment-269763463
Received on Friday, 30 December 2016 11:56:17 UTC