- From: Rimas <notifications@github.com>
- Date: Wed, 08 Feb 2017 13:07:13 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 8 February 2017 21:08:01 UTC
I think @watilde you must be careful with this issue: also consider case with `localhost`, for example: `file://localhost///foo/bar` It looks likes Edge and Chrome ignores slashes after `localhost`. If not, then this can cause a re-parsing issue: After first pass we will get: <b>href:</b> `file://///foo/bar` <b>pathname:</b> `///foo/bar` If now we try to parse <i>href</i>, then will get: <b>href:</b> `file:///foo/bar` <b>pathname:</b> `/foo/bar` Other test cases to try: `file:///localhost///foo/bar` `file:////localhost///foo/bar` -- 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/232#issuecomment-278461743
Received on Wednesday, 8 February 2017 21:08:01 UTC